You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 18, 2018. It is now read-only.
Currently in pypi repo just the version 2.0.2 is released; this is of 2011 and since them have been many commits in master and any new version.
I would like to propose a release 2.0.3 which includes just the patch for avoiding memory leaks (using weakrefs instead of normal dicts). you can see here: https://github.com/ealogar/python-gearman/tree/v2.0.3
For launching this PR and release a version I would propose to include the tag v2.0.2 in a new branch release v2.0.2
Another idea is to release a 3.0.0 pointing to current master branch.
In both cases I think a branch with version name in repo would be needed to propose patches to version.
Is it possible to do this?
The text was updated successfully, but these errors were encountered:
A performance test revealed that master version lose performance against release 2.0.3 (relasae 0.2.0 with weakref memory leak patch).
The performance test was done in a RHEL6 with 2 cores and 4 gigas of ram. Just a simple wsgi server exposed in uwsgi through unix sockets. The wsgi server just perform a single request in background (background=True, wait_until_complete=False) to a gearman server in another machine.
The gearman server is not saturated and uwsgi is able to launch more requests to wsgi app.
In the same conditions the v2.0.3 gives 1200 requests/second whereas master gives 830 TPS. Both branches not give errors
Currently in pypi repo just the version 2.0.2 is released; this is of 2011 and since them have been many commits in master and any new version.
I would like to propose a release 2.0.3 which includes just the patch for avoiding memory leaks (using weakrefs instead of normal dicts). you can see here:
https://github.com/ealogar/python-gearman/tree/v2.0.3
For launching this PR and release a version I would propose to include the tag v2.0.2 in a new branch release v2.0.2
Another idea is to release a 3.0.0 pointing to current master branch.
In both cases I think a branch with version name in repo would be needed to propose patches to version.
Is it possible to do this?
The text was updated successfully, but these errors were encountered: