|
Goin Down...
|
View this Thread in Original format
| DjSimonB |
| Anyone else noticing TA go slow/grind to a halt almost every day? Like, database errors and such. Or is it just me :conf: |
|
|
| jp |
| There are just too many of us online :nervous: |
|
|
| nchs09 |
| j00 is smokin the cr4ck f00l! |
|
|
| D-res |
| it does seem to be going slower than before and i do get some 'SQL database errors' or soemthign quite often. i dont know. sometimes it takes up to 4 minutes to load a thread, and i have 3 megabit internet cable connection |
|
|
| Sand Leaper |
| Yea, same thing over here too. Guess you just have to live with it when TA is as huge as it is. |
|
|
| enferno |
| pff . . i thought this was going to be anotha vagina thread |
|
|
| Rodrico |
| quote: | Originally posted by enferno
pff . . i thought this was going to be anotha vagina thread |
yeah, I thought so too, god damn tricky titles.. |
|
|
| trancebrat |
| quote: | Originally posted by Rodrico
yeah, I thought so too, god damn tricky titles.. |
You're back!!! |
|
|
| Rodrico |
| quote: | Originally posted by trancebrat
You're back!!! |
With my own internet in my own house...so im back for good. ;) |
|
|
| DjSimonB |
| quote: | Originally posted by Rodrico
yeah, I thought so too, god damn tricky titles.. |
Nothing wrong with making your thread titles a bit ambigously sexual :p |
|
|
| DJ_Bod |
| quote: | Originally posted by jp
There are just too many of us online :nervous: |
that's my guess. |
|
|
| Swamper |
| quote: | Originally posted by josh4
The user base is getting too big for the servers running TA. This site is getting more and more popular. Pretty soon they may have to upgrade their plan with whoever hosts the site or move to another host.
I keep getting a frequent error message from the boards saying there are too many connections. |
Not exactly - I just upgraded hardware a few weeks ago.
Running a 64k chunk size on the raid array seems to have offered little performance increase over the 32k it was at before -- using thttpd (a lightweight webserver) to handle image loading (instead of relying on resource-heavy Apache) allows me to turn Keepalive on -- meaning that when you connect to the server to get an image it keeps that connection open knowing that you'll soon request more images - rather than closing it after serving 1 image and re-opening it for each subsequent request.
Now, by freeing up Apache in this way (which used to bottleneck with excessive image/database/page requests) I now have a situation where incoming forum requests (Threads/posts/searches) can be queued in a greater number -- thereby causing bottlenecks on the database end more frequently.
I'm gonna change a couple of other things tonight and see what happens, but that's it in a nutshell. |
|
|
|
|
