|
|||
|
unfortunately you have given no information to help diagnose mysql problems since just saying your database is 300mb is not helpful. In the end it might not even be a database issue. Last week i had excessive i/o and i solved it by addressing my database with a large query cache and settings only to find 2 weeks later it was crawling and taking 10x times the cpu periodically. Turns out it was bad behavior script that was working ok a week ago.
Maybe it really isn't vpslink's fault... there's alot going on with webhosting.
__________________
Happily on a Link3. Feel free to request a refferal code that takes a 10% lifetime discount off your hosting. Please open a SUPPORT TICKET AND CALL vpslink to resolve your vpslink problems FIRST |
|
|||
|
Quote:
|
|
|||
|
ok, im pretty sure i have proved its vpslink here, ive moved the databases to another one of my vps servers with mysql configured the same and it all works perfectly, move it back to the db server and it goes slow....so as far as that tells me its vpslink's end as the server that it works best on is under alot more load than the db server is....
|
|
|||
|
It can be frustrating when you suspect reasons for performance related problems lie beyond your control and you are unable to troubleshoot.
So, if you want to get an idea of how your disk i/o is performing on your node, compare to these from mine: Code:
(link 4) $ time dd if=/dev/zero of=./1GB bs=1024 count=1024000; rm ./1GB 1024000+0 records in 1024000+0 records out 1048576000 bytes (1.0 GB) copied, 12.8043 s, 81.9 MB/s real 0m14.196s user 0m0.376s sys 0m3.160s Code:
(link 3) $ time dd if=/dev/zero of=./1GB bs=1024 count=1024000; rm ./1GB 1024000+0 records in 1024000+0 records out 1048576000 bytes (1.0 GB) copied, 41.3777 s, 25.3 MB/s real 0m42.600s user 0m0.376s sys 0m3.440s Code:
(link 2) $ time dd if=/dev/zero of=./1GB bs=1024 count=1024000; rm ./1GB 1024000+0 records in 1024000+0 records out 1048576000 bytes (1.0 GB) copied, 20.3884 s, 51.4 MB/s real 0m20.772s user 0m0.316s sys 0m3.000s Reviewing the above figures, the throughput on the link 3 does look a bit suspicious in that it is half of the link 2, but I don't have any historical data with which to make a comparative analysis...It could have always been this way. |
|
|||
|
chriss is really helpful. usually at this point I feel like it's pulling teeth with this matter. For example I still have no idea what cms/script you are using. is this a logged in user issue? Are you doing these tests during peak usage? For all I know it's just chance you switched to another vps when it was maybe just a search engine bombardment...
Not to say u aren't right and it isn't vpslink's fault. Maybe you can get danL to chime in. I know the support tickets really define what unmanaged is.
__________________
Happily on a Link3. Feel free to request a refferal code that takes a 10% lifetime discount off your hosting. Please open a SUPPORT TICKET AND CALL vpslink to resolve your vpslink problems FIRST |
|
|||
|
Quote:
|
|
|||
|
looks like i may have got somewhere
ive brought another vps on teh exact same plan and moved everything as it was onto this new one and it preforms perfectly. so it seems it defifntly was something on that vps so now just have to give it a litlte bit of time to make sure all working well then need to get a refund on the one with the issues Thanks for all your help guys |
![]() |
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|