Macon, thanks for the update.
M Gravlee wrote:jcummins wrote:There are problems here and either they don’t have the time, aren’t smart enough to get it right, or don't care.
It's definitely the aren't smart enough one! I and 6 computer guys in New Jersey (of all places) have spent hundreds of hours on this problem. The server operators in Dallas have swapped out all 12 gig of memory, the guys in NJ have swapped out the kernel. We've reconfigured mySQL database dozens of times. The last time at 9:52 pm last night.
The problem with search is that the software is set to limit searches when the server is overly busy. Which is bad, but much better than a server crash. Searches are very computer intensive since it must look through 600,000 posts. I could delete 300,000 of the older posts but I would rather fix the server problem.
I can assure you that I am much more frustrated than you are. I'm spending $500/mo on this giant server and it is doing worse than the old one. But I can assure you that I definitely do care and am working on it every day.
M Gravlee wrote: But if I really knew what the problem was it would be fixed. We're just guessing and changing one thing at a time.
Workinonit Farm wrote:M Gravlee wrote: But if I really knew what the problem was it would be fixed. We're just guessing and changing one thing at a time.
Sounds like Dr. House . One thing at a time, process of elimination. Hopefully the problem will be 'discovered' sooner than later.
Users browsing this forum: No registered users and 15 guests