Opened 7 years ago
Closed 7 years ago
#13020 closed enhancement (invalid)
Several Tracd instances running on one project to improve performance
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | web frontend/tracd | Version: | 1.0.15 |
| Severity: | normal | Keywords: | performance |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I am solving slow Trac performance caused possibly by a number of plugins but that's not important here.
One specific ticket displaying takes 5 secs, the same ticket displaying from two computers - 15 secs and the time grows to highs which are not acceptable…
When I create two web servers (tracd + Apache in this case) working on one SQLite database containing one Trac project then the time for the same ticket displaying from 2 computers is 5 secs when each computer uses different web server.
So the easiest way how to speed the Trac up seems to be several servers working on different ports or several web servers behind load balancer (e.g. Nginx) etc.
I did not find any word about such configuration yet. Is it supported? The database access seems to be OK but these several tracd instances are also writing into one environment, one log file, creating attachments in one folder etc. which I see as possible problem.
TIA Pavel
Attachments (0)
Change History (1)
comment:1 by , 7 years ago
| Milestone: | undecided |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
Please ask support/configuration questions on the MailingList.