Custom component running slowly after 2.5.8 to 2.5.18 - Joomla! Forum - community, help and support
hello, working on creating new version of custom component client, shows information directory on map in front end based on user selected categories. updating remake database structure improve performance, , part of moved site shared hosting provider vps account. on vps production site, example query can run takes 4 seconds complete. works follows:
-user selects list of categories results from
-component sends ajax request server
-component sql query, , gets results
-then takes these results , generates html each item based on results, , compiles whole set of data json
-sends json browser, javascript uses populate map results
the 4 seconds in test did noticably better on shared host, due resources being available. however, here strange happens. cloned site develop new version of application, focused around improving performance of it. once upgraded site 2.5.8 (which production site running) 2.5.18, same test took 32 seconds on average! also, selecting more few categories resulted in error 500 server on ajax call, stating pcre.backtrack_limit had been exceeded. bumped limit huge number , gives gateway timeout after 1.5 minutes.
nothing else had been changed on site, , double checked creating clone , doing timing tests before , after upgrading (always jumps 4 seconds 32 seconds, larger query , never finishes). seems somewhere between versions 2.5.8 , 2.5.18 has changed in joomla cause massive performance loss in application. note component not use regular expressions extensively (the 1 saw offhand optional case when field wasn't empty, , removing had no effect).
i realize don't give go on, error happening custom extension client after skipping 10 versions of joomla, , don't know part causing issue. extension isn't heavily using joomla libraries (any more normal) , main meat of sql query , loops iterate through results , storing html string variable. want know if else can think of me into, or if has changed in versions should into. checked changelog nothing jumped out @ me.
-user selects list of categories results from
-component sends ajax request server
-component sql query, , gets results
-then takes these results , generates html each item based on results, , compiles whole set of data json
-sends json browser, javascript uses populate map results
the 4 seconds in test did noticably better on shared host, due resources being available. however, here strange happens. cloned site develop new version of application, focused around improving performance of it. once upgraded site 2.5.8 (which production site running) 2.5.18, same test took 32 seconds on average! also, selecting more few categories resulted in error 500 server on ajax call, stating pcre.backtrack_limit had been exceeded. bumped limit huge number , gives gateway timeout after 1.5 minutes.
nothing else had been changed on site, , double checked creating clone , doing timing tests before , after upgrading (always jumps 4 seconds 32 seconds, larger query , never finishes). seems somewhere between versions 2.5.8 , 2.5.18 has changed in joomla cause massive performance loss in application. note component not use regular expressions extensively (the 1 saw offhand optional case when field wasn't empty, , removing had no effect).
i realize don't give go on, error happening custom extension client after skipping 10 versions of joomla, , don't know part causing issue. extension isn't heavily using joomla libraries (any more normal) , main meat of sql query , loops iterate through results , storing html string variable. want know if else can think of me into, or if has changed in versions should into. checked changelog nothing jumped out @ me.
have created joomla 2.5.18 on same server? i'm asking because environment might different.
in case, best can enable slow query log on mysql , run script again , see log has. likely, query causing problem there.
there serious performance issues in joomla 2.5. might interested in reading post: http://www.[removed self promotion].com/how-we-optimized-a-large-joomla-2-5-website-and-made-it-over-200-times-faster
in case, please report findings (maybe print slow query) here others can learn experience. thanks!
in case, best can enable slow query log on mysql , run script again , see log has. likely, query causing problem there.
there serious performance issues in joomla 2.5. might interested in reading post: http://www.[removed self promotion].com/how-we-optimized-a-large-joomla-2-5-website-and-made-it-over-200-times-faster
in case, please report findings (maybe print slow query) here others can learn experience. thanks!
Comments
Post a Comment