You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "David Johnson (JIRA)" <ji...@apache.org> on 2010/07/19 03:21:50 UTC
[jira] Resolved: (ROL-686) Very slow performance - many queries
[ https://issues.apache.org/jira/browse/ROL-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Johnson resolved ROL-686.
-------------------------------
Resolution: Won't Fix
No longer relevant. Those hierarchical fields were removed from Roller.
> Very slow performance - many queries
> ------------------------------------
>
> Key: ROL-686
> URL: https://issues.apache.org/jira/browse/ROL-686
> Project: Roller
> Issue Type: Bug
> Components: Database Access & Data Model
> Affects Versions: 1.0RC2
> Environment: Apache 2.0.48 / Tomcat 5.0.28 / PostgresQL 7.4 / Double Processor / 2GB
> Reporter: Thomas De Vo
> Assignee: Roller Unassigned
>
> Tomcat uses extensive CPU during transactions: up to 100%.
> The following are figures from development:
> When for the first time a blogger page is requested with 2 entries, 78 queries are issued, taking 16 seconds, the second time around there are 7 queries issued, taking 1 second.
> A blogger page with 7 entries on it needs the first time around 103
> queries, taking 21 seconds, the second time around 12 queries which are good for 2 seconds.
> The blogger homepage requires 164 queries the first time around, good for 29 seconds, the second time around the homepage can be build with "only" 59 queries, good for 18 seconds.
> During these times the CPU goes up to 100% utilisation.
> JRoller is configured to make use of the standard Tomcat connection pooling.
> During a certain load of the system, tomcat needs restarting (probably waiting for system resources).
> Timings mentioned are measured within postgresql database, they do not include any application processing times.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.