Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Memcache is more along the lines of a distributed object cache vs something like APC or XCache, which stores PHP bytecode in memory so you avoid having to parse it each time. Their main purposes are different.</p> <p>For example, if you had a very CPU intensive database query that people often requested, you could cache the resulting object in memcache and then refer to it instead of re-running that query all the time. </p> <p>APC &amp; XCache do have similar object caching features, but you are limited to the host machine. What if you wanted 10 different servers to all have access to that one object without having to re-do the query for each server? You'd just direct them to your memcache server and away you go. You still get a benefit if you only have a single server because using memcache will help you scale in the future if you need to branch out to more boxes.</p> <p>The main thing to consider is if you think your app is going to need to scale. Memcache has more overhead since you have to use a TCP connection to access it, versus just a function call for APC/Xcache shared objects. </p> <p>However, Memcache has the following benefits:</p> <ul> <li>Faster than the disk or re-running query.</li> <li>Scales to multiple servers.</li> <li>Works with many different languages, your objects are not locked into PHP + APC/Xcache only.</li> <li>All processes/languages have access to the same objects, so you don't have to worry if your PHP child processes have an empty object cache or not. This may not be as big a deal if you're running PHP-FPM though.</li> </ul> <p>In most cases, I would recommend caching your objects in memcache as it's not much harder &amp; is more flexible for the future.</p> <p>Keep in mind that this is <strong>only</strong> regarding caching objects. Memcache does <strong>NOT</strong> have any bytecode or PHP acceleration features, which is why I would run it side-by-side with APC or Xcache</p>
    singulars
    1. This table or related slice is empty.
    1. POCan I use APC AND memcached on the same server?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKlinky
    1. USKlinky
    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. CO"You still get a benefit if you only have a single server because using memcache will help you scale in the future if you need to branch out to more boxes." -- so there's no benefit on a single server?
      singulars
      1. PO
      1. USnickf
    2. CO@nickf, added more detail to my answer.
      singulars
      1. PO
      1. USKlinky
    3. CO+1. Another point to add: APC does not handle high-concurrency as well as memcached does. We use both memcached and APC in production, for storing appropriate application data -- and we're considering starting to use Redis as well (for persistence, and list operations). At high levels of concurrency, each one is good at certain things that the others aren't.
      singulars
      1. PO
      1. USFrank Farmer
 

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