An update... When we reinstalled TapaTalk and updated the software and hooks associated with the latest release, our server load exploded by approximately five times. And it has been fairly consistent at that load level since. As we increase connections approaching 900 to 1,000 users the system gets very slow. Some will see a 503 error and will continue to see 503 errors until we can get some of our architecture rearranged. I just want everyone to know that until we can make those changes, things could get flaky. And there might be times at peak loads, that we will shut down access via TapaTalk and searches from the various search engines in order to keep content flowing to our registered members. This is a dual post.

I don't use TapaTalk ... did't even know what it was until now (mobil app - oh boy) ... I have seen a few posts with that TapaTalk signature but not many (certainly a minority) so I'm guessing TapaTalk connections remain "active" even with the end user has long since turned "off" (virtual off not a real power down) their mobile device and/or is not viewing the site?  Hence the massive increase in load?  

 

Or is TapaTalk really just a distributed data miner that's always running?  Convertering an end user's device into a web server bot?

 

Perhaps when loads go up you can shutdown TapaTalk access?

 

Rob

 

 

Perhaps when loads go up you can shutdown TapaTalk access?

 

Rob, yes, we can do that. We are working with the TapaTalk Devs to figure out where the issue lies.

Thanks, Tom, for all the work you're doing. Much appreciated.

Is there any hard number for the folks who use TapaTalk? I did install the version for my Windows Smart Phone just to try it out, and frankly can't be bothered with it...

...of course, the only times I'm not sitting at or near one of my home computers is when I'm driving the occasional grocery store run, during which times I couldn't really use it anyway! :lol: