##// END OF EJS Templates
pull-requests: increase stability of concurrent pull requests creation by flushing prematurly the statuses of commits....
pull-requests: increase stability of concurrent pull requests creation by flushing prematurly the statuses of commits. This is required to increase the versions on each concurrent call. Otherwise we could get into an integrity errors of commitsha+version+repo

File last commit:

r3018:26521a96 stable
r3408:2a133f7e stable
Show More
tuning-user-sessions-performance.rst
66 lines | 2.2 KiB | text/x-rst | RstLexer
/ docs / admin / tuning-user-sessions-performance.rst
docs: updated docs about session tunning, and fixed DB tunning guide.
r1292 .. _user-session-ref:
docs: updated scaling/cluster docs
r3018 User Session Performance
------------------------
docs: updated docs about session tunning, and fixed DB tunning guide.
r1292
The default file-based sessions are only suitable for smaller setups, or
instances that doesn't have a lot of users or traffic.
They are set as default option because it's setup-free solution.
The most common issue of file based sessions are file limit errors which occur
if there are lots of session files.
Therefore, in a large scale deployment, to give better performance,
scalability, and maintainability we recommend switching from file-based
sessions: update session tunning instructions.
r2851 sessions to database-based user sessions or Redis based sessions.
docs: updated docs about session tunning, and fixed DB tunning guide.
r1292
To switch to database-based user sessions uncomment the following section in
your :file:`/home/{user}/.rccontrol/{instance-id}/rhodecode.ini` file.
.. code-block:: ini
## db based session, fast, and allows easy management over logged in users
beaker.session.type = ext:database
beaker.session.table_name = db_session
docs: updated scaling/cluster docs
r3018 # use just one of the following according to the type of database
docs: updated docs about session tunning, and fixed DB tunning guide.
r1292 beaker.session.sa.url = postgresql://postgres:secret@localhost/rhodecode
docs: updated scaling/cluster docs
r3018 # or
docs: updated docs about session tunning, and fixed DB tunning guide.
r1292 beaker.session.sa.url = mysql://root:secret@127.0.0.1/rhodecode
beaker.session.sa.pool_recycle = 3600
beaker.session.sa.echo = false
and make sure you comment out the file based sessions.
.. code-block:: ini
## types are file, ext:memcached, ext:database, and memory (default).
#beaker.session.type = file
#beaker.session.data_dir = %(here)s/data/sessions/data
sessions: update session tunning instructions.
r2851 The `table_name` will be automatically created on specified database if it isn't yet existing.
Database specified in the `beaker.session.sa.url` can be the same that RhodeCode
uses, or if required it can be a different one. We recommend to use the same database.
To switch to reds-based user sessions uncomment the following section in
docs: updated docs about session tunning, and fixed DB tunning guide.
r1292 your :file:`/home/{user}/.rccontrol/{instance-id}/rhodecode.ini` file.
.. code-block:: ini
sessions: update session tunning instructions.
r2851 ## redis sessions
beaker.session.type = ext:redis
beaker.session.url = localhost:6379
docs: updated docs about session tunning, and fixed DB tunning guide.
r1292
and make sure you comment out the file based sessions.
.. code-block:: ini
## types are file, ext:memcached, ext:database, and memory (default).
#beaker.session.type = file
#beaker.session.data_dir = %(here)s/data/sessions/data