<br><br><div class="gmail_quote">On Wed, Jan 19, 2011 at 5:50 PM, Evan Horne <span dir="ltr"><<a href="mailto:Evan_Horne@umit.maine.edu">Evan_Horne@umit.maine.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
After upgrading from 3.9.7 to 4.0.0rc1 and then 4.0.0rc2, I was experiencing similar slowdown compared to 3.9.7.<br>
I initially assumed the slow response was because I have RT currently running on a virtual machine on a desktop, but that doesn't explain why 3.9.7 was seemed so much more responsive on the same VM.<br>
<br>
I grabbed the output with MasonX::Profiler enabled for both 4.0.0RC1 and 4.0.0RC2 while loading a page while this issue was occurring. I reverted my VM to an old state with RT3.9.7 installed and tried to enable MasonX::Profiler, but it wasn't<br>
producing any extra output for some reason. I'd be happy to play around with it some more to get it working if anyone would find that information useful.<br>
<br>
Devel mode is off in both of these instances. No more than a couple of tickets total in the database. A clean RT_SiteConfig file with nothing but MasonX::Profiler enabled doesn't seem to make any difference in page loads. The client is Firefox.<br>
<br>
4.0.0 RC1 Output: <a href="http://pastebin.com/xUHP07nz" target="_blank">http://pastebin.com/xUHP07nz</a><br>
4.0.0 RC2 Output: <a href="http://pastebin.com/kFxr0Cg8" target="_blank">http://pastebin.com/kFxr0Cg8</a><br>
<br>
I grabbed the above output before reverting back to 3.9.7. Odhiambo's log also shows a long time being taken to process /Elements/HeaderJavascript as in my logs.<br>
<br>
After playing around with RT 3.9.7 for a little bit and not getting the extra output from MasonX::Profiler, I reverted my VM back to it's current state with RT 4.0.0RC2 running and for some odd reason, it's now running faster than 3.9.7 was without<br>
any additional changes. At this point I'd be willing to chalk up my own experience to a system configuration issue on my end, but if Odhiambo is still experiencing a similar issue, it may be related.<br>
<br>
It never occurred to me to try Chrome's resource tracking feature while I was experiencing the issue to see where the delays were coming from on the client end until after it had resolved itself.<br>
<br>
Just thought I'd throw out my experiences so far. If I can be of any further assistance, let me know.<br><br></blockquote><div><br><br>I am still stuck with this problem, and not sure what is my next move.<br> <br></div>
</div><br>-- <br>Best regards,<br>Odhiambo WASHINGTON,<br>Nairobi,KE<br>+254733744121/+254722743223<br>_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ <br>Damn!!<br><br>