Please Scroll Down to See Forums Below
napsgear
genezapharmateuticals
domestic-supply
puritysourcelabs
UGL OZ
UGFREAK
napsgeargenezapharmateuticals domestic-supplypuritysourcelabsUGL OZUGFREAK

So what was the fix?

HappyScrappy

New member
the board was slow. then it was upgraded and was REALLY slow.
then it magically got tolerable again...

so what ended up being the fix? taking out all the "sleep(58)" statements? :)
 
lol

and on a side note, the RAID array wouldn't increase performance, it would instead increase reliability :)

(although they tend to be on SCSSI drives, so if you were going to that after and IDE/EIDE, you would get more performance)
 
Just spoke to Jorge.

George said he just poured some Triple Threat 3/60 right into a funnel located on the top of the server and it is running ridiculously fast.

He also said the server put on 27 pounds in the last 39 hours.

He will have the lab tests back tomorrow.

He also mentioned that he is having a sale on Triple Threat 3/60...sounds kind of fishy.
 
Last edited:
How about adding a shitload of memory to the DB machine, maybe re-indexing the damn DB, or maybe putting the DB and webserver on different boxes? That's what I'd try.

I'm also curious what they did to fix it.
 
strong island said:
Just spoke to Jorge.

George said he put poured some Triple Threat 3/60 right into a funnel located on the top of the server and it is running ridiculously fast.

He also said the server put on 27 pounds in the last 39 hours.

The miracle effectivness of carbohydrates....lol
 
I was wondering the same thing and emailed George about this the other day. He wrote back telling me that one of the servers had a malfunctioning keneuter valve they had to replece.
 
George says..."Its in there!!"

Triple Threat

Ingrediants: Whey protein isolate, maltodextrin, polydextrose, yellow #15, stevia, cocaine, alpha lipoic acid, people, creatine monohydtrate and George's secret shiznit(proprietary formula.)
 
jnuts said:
How about adding a shitload of memory to the DB machine, maybe re-indexing the damn DB, or maybe putting the DB and webserver on different boxes? That's what I'd try.

I'm also curious what they did to fix it.


while I agree that this is a database driven site - I've posted before why I didn't think the issue was with the DB.
The only DB issue I would suspect was if it was on the same physical server as the web/app server.

if you look at the execution chain of what goes into each page load - the database is a very small part.
 
HappyScrappy said:
the board was slow. then it was upgraded and was REALLY slow.
then it magically got tolerable again...

so what ended up being the fix? taking out all the "sleep(58)" statements? :)

Evidently the database was getting "constipated" and they fixed stuff and it now poops fine.

I am not making this up.

-Warik
 
Re: Re: So what was the fix?

Warik said:


Evidently the database was getting "constipated" and they fixed stuff and it now poops fine.

I am not making this up.


LOL

hmm - sounds like a threading issue in mySQL then... odd that it worked before - perhaps that there was a new install and someone skipped that step accidentally
 
Top Bottom