Skip to content

Commit 5be5411

Browse files
authored
RAM observations
1 parent 1823e2c commit 5be5411

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

benchmarks.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -161,6 +161,8 @@ At the same time, plpython2u-based function showed very similar (sometimes even
161161

162162
There is practically no difference between plpython2u and plpython3u functions.
163163

164-
The bottom line: the [pgsql-http](https://github.com/pramsey/pgsql-http) doesn't seem to perform better than plpython2u function. The plpython2u-based approach wins because:
164+
The bottom line: the [pgsql-http](https://github.com/pramsey/pgsql-http) doesn't seem to perform better than plpython2u function. However, pgsql-http is better in terms of memory consumption (in the examples above, postgres+plpythonu took ~20% more RAM than postgres backends with pgsql-http; for plsh, postgres backend combined with curl process took the same RAM resources as postgres+plpythonu backend).
165+
166+
The plpython2u-based approach wins because:
165167
- it's not slower than pgsql-http
166168
- it's much easier to deploy.

0 commit comments

Comments
 (0)