Changes between Version 24 and Version 25 of TracPerformance

Timestamp:

Feb 13, 2021, 11:40:11 AM (3 years ago)

Author:

figaro

Comment:

Cosmetic changes

TracPerformance

@@ -80 +80 @@
 == Database
 
- - Use PostgreSQL or MySQL for many users to avoid lock contention.
+ - Use PostgreSQL or MySQL in an environment with many users to avoid lock contention.
  - Otherwise consider using SQLite with connection string `sqlite:db/trac.db?journal_mode=wal&synchronous=off` if tolerable. (#11967)
 
 == Unsorted
  
- - There was a bug up to 0.11.4 which could cause 100% CPU usage once in a while on some platforms (#7785, thought to be fixed in 0.11.5, but re-opened since).
- - Some plugins seem to have a high impact on the performance, see ["TracDev/Performance/0.11.5#customizationsandplugins"].
- - Trac's [query:status=!closed&keywords=~performance performance issues].
+ - There was a bug up to 0.11.4 which could cause 100% CPU usage once in a while on some platforms. See #7785, which was thought to be fixed in 0.11.5, but re-opened since.
+ - Some plugins seem to degrade performance, see ["TracDev/Performance/0.11.5#customizationsandplugins"].
+ - Trac's [query:status=!closed&keywords=~performance tickets regarding performance].
 
 == Profiling a Trac request