Capacity

topic posted Thu, September 17, 2009 - 11:30 AM by  offlineGlen
Share/Save/Bookmark
Advertisement
First of all, thank you for all the hard work you are doing in keeping this place running.

I happen to really like it here.


I always see in the bug reports that tribe is "over capacity"
what IS the capacity? How many people or operations can go on at one time? is there an actual number?

just curious.
posted by:
Glen
Los Angeles
Advertisement
Advertisement
  • Re: Capacity

    Thu, September 17, 2009 - 11:54 AM
    750 simultaneous connections is the current maximum capacity when all 10 servers are online. At any given time one or two servers are usually out for testing or other issues. This month we're averaging about 200,000 hits an hour, which works out to about 55 hits per second. However, some transactions take longer than a second to complete (pulling up long threads, for instance...), most averaging 2-4 seconds, and so things backup. Add to that the inherent instability of the Java platform it's running on that causes the servers to restart frequently at times... plus we're suspecting we may have hit a bug on the load balancer with the current session issue that's bouncing people around the servers. Using "remember me" will definitely improve your experience here.
    • Re: Capacity

      Thu, September 17, 2009 - 12:07 PM
      thank you for the details. lacking these types of details, leaves us to guessing and discontentment. having details makes one feel like you folks care. important for a social network.
    • Re: Capacity

      Thu, September 17, 2009 - 12:09 PM
      Wow. That isn't very much. So, actually, due to threading issues, the maximum connections is approximately 250/second. That's not good at all for a social network. OkCupid, for instance, frequently has 15000 logged in users simultaneiously, many of them doing chats...or so it is rumored.
    • Re: Capacity

      Thu, September 17, 2009 - 1:27 PM
      Looking at the 'browse people" page, there are reported to be over 260,000 members. This means that only about .28% (a little over a quarter of one percent) of the members can be online simultaneously. That is a very small capacity! No wonder the servers keep being maxed out... resulting in either poor performance or outright refusal of connections.

      What proportion of the membership is reasonably expected to be accessing the site simultaneously? What is the optimal capacity for a social site such as this, in terms of percentage of membership? Including enough overhead so as to not routinely be exhasuting so much of the capacity that performance is not degraded.

      I've long suspected Tribe's problems arise out of basic scalability issues.


    • Re: Capacity

      Fri, September 18, 2009 - 6:48 PM
      <750 is the current maximum capacity >

      *shocked*
      *totally shocked*

      That explains a lot.

      And is very limiting
      • Re: Capacity

        Fri, September 18, 2009 - 6:58 PM
        I don't see any point in even trying to expand membership with this limited capacity.

        According to the web tacking site Alexa, 66% of sites are faster in load time, too.

        Daily traffic also tanked in one day on September 16 ~ two days ago. I do not think that is a coincidence.

Recent topics in "Tribe.net Bug Reports"