Forum issues

Indubitably. I myself am also having a long time to wait when posting, and have already created a thread about it (look at profile), there was some talk bout C A and B class networks or some shit like that, uhh I don’t know what that means its three am and I am not writing without any punctuations.


Um right, it is late, err, early, err, something like that. Get forums speeded up, I think it is a database access problem.

But at least the search is back! Thanks, Rhino!

quote:

---

Original post by LordShade
Anyway, think I saw a post on possible replacement of the forums so my comments may be moot.

---

Indeed. We believe the replacement will offer better performance.

from the bottom of my heart: thank you.

i just hope the servers dont get an extreme amount of strain on them.

btw: (to admins) if you dont mind me asking, what searching API/System do you use? is it in-house or 3rd partie or what?

also... (darn cureosity) about how large (in megabytes or whatever) are your databases alltogether (tables, cells, ...) or just one of the largest ones. thanks.

An error occurred on the server when processing the URL. Please contact the system administrator. x6!

quote:

---

Original post by AfTeRmAtH
btw: (to admins) if you dont mind me asking, what searching API/System do you use? is it in-house or 3rd partie or what?

---

The (new forum) search (not the one you can access right now) is a combination of a background indexing system written by Mike Tanczos in C++ and a somewhat complex stored procedure (also written by Mike) to do queries. The search does relevence sorting and has about the same response time as Google. The current search (unless Dave has made a big, unnoticable change) uses the built-in capabilities of the database (which were never really meant to be used for text searchs on huge datasets)

quote:

---

also... (darn cureosity) about how large (in megabytes or whatever) are your databases alltogether (tables, cells, ...) or just one of the largest ones. thanks.

---

The unit of measurement you are looking for is "gigabytes" and the word you are looking for is "table". Our problems don''t have much to do with ASP/PHP, they have to do with SQL trying to do operations on table>RAM. All the fast pages are actually cached or use stored procedures, the semi slow pages (like the profile) are using standard read only SQL operations, and the ones that time out (the error you get) are those which actually try to write to one of the big tables (though if there is a ton of traffic some of the other scripts can time out too).

quote:

---

Original post by Michalson
The current search (unless Dave has made a big, unnoticable change) uses the built-in capabilities of the database (which were never really meant to be used for text searchs on huge datasets)

---

Come to think of it, I''m sure that''s why people are suddenly getting more 500 errors lately (since I re-enabled the search about a weak ago).

quote:

---

Original post by Michalson
The unit of measurement you are looking for is "gigabytes" and the word you are looking for is "table".

---

Thats not big. Really.

quote:

---

Our problems don''t have much to do with ASP/PHP, they have to do with SQL trying to do operations on table>RAM.

---

On what server software? MySQL? Just curios - this should not be a problem at all. It sounds like ridiculous SQL or a very bad software.



Regards

Thomas Tomiczek
THONA Consulting Ltd.
(Microsoft MVP C#/.NET)

I''m slightly tired and overworked, but can I suggest a search by email?

Since the search is straining your servers, you can mitigate it by having a search by email.

Just type the search string, and then an email address, and whenever the servers can handle it, do the search and return the response by email.

It would help a lot with load balancing, and the response time would be minimal during normal times, and when gamedev is overworked, the response time would be slower anyways using the current search...

quote:

---

Original post by Michalson
... and the ones that time out (the error you get) are those which actually try to write to one of the big tables (though if there is a ton of traffic some of the other scripts can time out too).

---

I have this problem consistently ("An error occurred on the server when processing the URL. Please contact the system administrator.") when posting.

Doesn''t seem to matter what time of day it is, but every time I post I have to try, on average, three times before it goes through.

The first time I tried to post, I got this, and almost decided that it was an incompatibility problem (I use Opera, and many sites are poorly coded and can''t handle non-IE browsers). Luckily I tried a few more times...

What''s the isolation level on all of the transactions? It doesn''t seem to me that any process writing to the DB could possibly timeout (given that it looks to be a 30 second timeout). Maybe some of the reads or searches are accidentally locking the tables for r/w access?

Second try on this posting.