AppDB performance issue

[Nick Law]

Nick Law wrote:
> Tony Lambregts wrote:
>> Chris Morgan wrote:
>>  
>>> On 2/11/07, Tony Lambregts <tony.lambregts at gmail.com> wrote:
>>>    
>>>> Nick Law wrote:
>>>>      
>>>>> Hi Tony,
>>>>> Just lately, I've noticed that AppDB seems to be very slow, i.e it 
>>>>> can
>>>>> take15 seconds or more for a page to come up or simply to login. Is
>>>>> there a bandwidth problem or is the server getting overwhelmed or is
>>>>> it a problem at my end (UK). 30 seconds later it's back to being very
>>>>> responsive as if the server was a bit overloaded for 30 seconds or 
>>>>> so.
>>>>> Other websites I try at the time work fine including winehq. Is 
>>>>> winehq
>>>>> on a different server ?
>>>>>
>>>>>         
>>>> I have noticed this too and it is very annoying. Yes www.winehq.org
>>>> qpdb.winehq.or and bugs.winehq.org are all on the same server.
>>>>
>>>> Winehq and bugzilla are quite snappy but the AppDB is a pig now.
>>>>
>>>> I have know idea what is wrong
>>>>
>>>> -- 
>>>>
>>>> Tony Lambregst
>>>>
>>>>
>>>>
>>>>       
>>> Are particular pages slow? I'm not seeing slow page loads to the main
>>> page or to an application version page from here, a few seconds for
>>> each.
>>>
>>> Chris
>>>
>>>
>>>     
>>
>> I see it when doing administration ie accepting or rejectiong 
>> applications and
>> versions (maybe its the way we send emails).
>>
>>
>> -- 
>>
>> Tony Lambregts
>> .
>
> Yes, ditto. Logging in to do admin tasks, but not only that, if I 
> click on the link in an email from somebody that has posted to the 
> WoW  2.0.x page it will take 30 seconds for the page to appear.
>
> I just posted some replies to the wow page and then clicked on the 
> link in the email and it took 84 seconds for the page to appear. It 
> find it seems to be more frequent now, maybe every other page or 1 in 
> three pages are very slow.
>
> Nick
>
>
Correction it seems to be bad at the moment, the last 4 pages are slow, 
60-90 secs before they display, and now it's back to < 2seconds to 
display a page again, it's like some process on the server hogs the CPU 
for 60 secs intermittently.

Nick