this happens very often... i have a hunch it's during peak load hours. 

Same problem here. Site not responding at all or some error about maximum process limit exceeded, or something. Or a recursive SQL error. 

i have a hunch it's during peak load hours.

Yes, it happened very often in the afternoon (French time)... and it's boring... Is there a way to avoid this issue ? 

Go finish your map JPL. =) 

It's "cooking"... don't worry ;) 

func is fast like F1 :) 

Nevertheless I get a "URL cannot be reached" message this morning... weird... 

today too, half of time doesn't load at all 

in the evenings (europe), it more often than not:
1) doesn't load at all
2) gives internal error (process limit exceeded)

It works really only in off-load hours. Which sucks. Are there any actions in planning?

Cause this board rocks and I hope good stuff will be kept going on in here. (Just look at the latest goings in mapping help for example!) 

when it works fairly fine, it's intolerably slow when being logged in. why this difference?
btw. what about a 'mark all threads read' option? 

when it works fairly fine, it's intolerably slow when being logged in. why this difference?
btw. what about a 'mark all threads read' option? 

when it works fairly fine, it's intolerably slow when being logged in. why this difference?
btw. what about an 'mark all threads read' option? 

 

FYI, func_ works faster when you access as guest (unlogged)... no "url cannot be reach", no "no internal error"... Metlslime ? Any idea ? 

.. I just got at least "recursive SQL error" he he he... 

when it works fairly fine, it's intolerably slow when being logged in. why this difference?
btw. what about an 'mark all threads read' option 

There is a difference between being logged in and logged out -- logged in people get a SQL query which includes their userid when visiting forum.php, while anonymous users get one that doesn't contain a userid. MySQL caches queries, so if you're not logged in, there's a good chance that your queries will have already been processed for someone who visited just before you, and so it can come out of the cache, which is a lot faster.

But this doesn't mean as much for the news page, the view_thread page, etc. 

it fucks up most of the time, even if you're on a computer with no cookies - thus unlogged. It won't load func, either you get a zero sized reply or timeout or process limit exceeded. 

What's happening today ?! It's working so fast I can't remember when it happened last time... ;)
Did you change anything in your php code ?
Nevertheless, it's cool to see all is workig fine now... I hope it will be stable more than today :P 

 

...might be faster now. Thanks to Sleepwalkr for the tips.

Let's try it out this week and let me know how good/bad things are. 

It seems quite a bit faster than it has been for some time now. But still not like it used to be, but a definite improvement over recent times, for me thus far anyway. 

*crosses fingers*

maybe i can post more than just random links now ^_^ 

just had one of those recursive sql errors again? 

There has definitely been a nice improvement since the changed DB code. I have had no errors, and the site has loaded everytime I tried to access it; albeit frequently it still takes five seconds to get a response.