Sam Leong, this is a picture of your f. database

[Rogue Trader]

slow, underpowdered and always hang :oIo:

 

[Rogue Trader]

another one, el cheapo.

 

[Watchman]

hahahaha ...

his server very popular over the last few minutes .

 

[cooleo]

 

[cooleo]

 

[angie II]

​

 

[Alamaking]

LOL, Fucking awesome, keep it coming, whahaha, this is funny

 

[cooleo]

​

 

[Watchman]

 

[Rogue Trader]

Another one for you. since your F database always kenna 'hack' like these losers below. Ha ha ha ha

 

[cooleo]

Sam, the museum called! They want their antique machine back!

 

[angie II]

​

 

[Boliao]

It's not Sam's website. Try using Ninjacloak if you think the site is slow and you'll be amazed how fucking fast it is even when going through a proxy.

It's the Service Provider, stupid.

 

[flkyflky]

slow, underpowdered and always hang :oIo:

I love this pic. This is Sam's POOR ASS!

 

[Shin Orochi]

It's not Sam's website. Try using Ninjacloak if you think the site is slow and you'll be amazed how fucking fast it is even when going through a proxy.

It's the Service Provider, stupid.

It's not your ISP when you get the database error message.

 

[uncleyap]

Sam can consider to have his MYSQL sever running in a separated box apart from the same box hosting Apache & PHP during next upgrade.

That is to setup a new server box within the same data center, running only MYSQL dedicated, link via 1000BT ethernet to the existing box, through standard TCPIP port #3306. Migrate the SQL DB over there from existing box, and point this V-bulletin's PHP over to the new box for database. Once working drop the SQL DB & turn off the MYSQL Server at localhost. From then onwards this box will be only the Apache web & PHP server only. SQL database is in another stronger box with more RAM & CPU power.

This is going to $$$cost$$$ few hundred more per month.

So sell ads space to cover?:p

For a V-Bulletin forum like this, usually Apache is not so big overhead for CPU & RAM (only WAN bandwidth mainly). PHP is slightly more CPU & RAM (heavier on CPU side). MYSQL is the main consumption of RAM & CPU resources in this case. It is not so bad at the beginning when the database is small, when we guys posted more and more and number of user A/C increased, the load expands exponentially upwards on CPU & RAM, taken to do each SQL search & update. I know that Sam got customized scripts to anti-spam and clean up this forum besides the regular V-bulletin PHP scripts, do not under-estimate these things, they can take up more CPU + RAM on the MYSQL side, surely also load down the PHP or whatever script host which Sam's script are written in, I assume it is PHP, but can be Perl or Ruby or anything.

 

[myo539]

Yes, suka suka give bloody infractions - don't know what the fucking meaning he has in his mind!

 

[Alamaking]

 

[Alamaking]

Ah Leong, this is your fuck up connection at this time. Cheapo server, pui!!!!!!
:oIo::oIo::oIo:

 

[diversifyx2]

Yes, suka suka give bloody infractions - don't know what the fucking meaning he has in his mind!

He is another attention seeker. lmfao