Skip to content

Commit 2f00f26

Browse files
authored
polish conclusions
1 parent 1b55c80 commit 2f00f26

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

benchmarks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -323,6 +323,6 @@ There is practically no difference between plpython2u and plpython3u functions.
323323
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).
324324

325325
The plpython2u-based approach wins because:
326-
- it's not slower than pgsql-http
326+
- it's definitely not slower than pgsql-http (sometimes even faster)
327327
- it's much easier to deploy.
328328
- RAM consumption is not signifcantly worse than in case of pgsql-http

0 commit comments

Comments
 (0)