Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In addition to Alix's answer, you may be interested in checkout out this article:</p> <ul> <li><a href="http://lists.danga.com/pipermail/memcached/2006-June/002384.html" rel="noreferrer">Memcached as a Sessions Store (etc)</a> by a Digg employee (Nick: timeless).</li> </ul> <p>A short excerpt:</p> <blockquote> <p><strong>What prompted the Memcached as sessions store:</strong></p> <p>Shortly after the rollout of Digg v3, the non-redundant MySQL session store hardware crashed. This led to a Digg outage. We had always planned that in such a case we would just roll a (trivial) change to put sessions into Memcached rather than MySQL to see how it fared.</p> <hr> <p><strong>So, before you were hitting the db every time for sessions?</strong> </p> <p>Yes.</p> <p>MySQL was plenty capable of keeping up with the inserts and selects done to deal with sessions. Our problem was actually with clearing out old sessions. The script to delete old sessions, despite being fairly sophisticated in its attempts to not overload the sessions database, still affected it.</p> <p>We surmise that Memcached will remove expired sessions with less overhead than MySQL.</p> <hr> <p>We used InnoDB for sessions [before memcached]. It wasn't table- or row-level locking. It was OS-level contention. Using Memcached in front of MySQL would've reduced the load and allowed the admin script to do its work, but that highlights the question: why even have MySQL behind memcached at all? We don't need or even want non-volatile sessions. (Important note to reader: you may need or want non-volatile sessions).</p> </blockquote> <p>"Why even have MySQL behind memcached at all?"... "We don't need or even want non-volatile sessions".</p>
    singulars
    1. This table or related slice is empty.
    1. POHow digg (or other high load category websites) are storing user sessions?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDaniel Vassallo
    1. USDaniel Vassallo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYeah, thank your for this article... Right now I'm taking a look at slideshow http://www.slideshare.net/folke/netlog-what-we-learned-about-scalability-high-availability-430211 (about Netlog architecture). There are also some slides about it...
      singulars
      1. PO
      1. USKirzilla
    2. CO+1 for link to Digg story
      singulars
      1. PO
      1. USnamespaceform
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload