Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Caching is a broad term that can happen at a number of different points. The optimum solution may be a combination of some or all. </p> <p>For example, you can add page, or output caching as described <a href="http://msdn.microsoft.com/en-us/library/06bh14hk.aspx" rel="nofollow" title="here">here</a>, which caches output on the web server, which I think is what you were referring to.</p> <p>In addition, you can cache the data in memory using something like <a href="http://memcached.org" rel="nofollow">memcached</a>, so that your data is more available to the web server as it builds the page, but you need to look at cache hit rate to know for sure that you are caching the right data.</p> <p>Also, although slightly off the topic of improving db heavy pages, you can cache static resources that change infrequently like images, css and include files using a content delivery network. Any CDN will almost certainly have a higher bandwidth and a cheaper data plan than your own connection because of the economies of scale, so the more of your content you can serve from there the better, in general.</p> <p>Your first question was "I was wondering if it's worth "caching" a static version of these pages". I guess the answer to that depends on whether there is a performance problem at the moment, and where the cause of that problem is. If the pages are being served quickly and reliably, then quite possibly it's not worth implementing caching. If there is a performance problem, then where is it? Is it in db read time, or is it in the time spent building the page once the data has been returned?</p>
    singulars
    1. This table or related slice is empty.
    1. POIs caching a good idea? If so, where?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJustABitOfCode
    1. USJustABitOfCode
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs caching a good idea? If so, where?
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your input. I think I'm looking at caching at the web server level. Memcached and CDNs are a great solution, but seem to be for higher volume sites (IMO), with distributed web servers, etc. I think they are both over the top for me right now.
      singulars
      1. PO
      1. USElad Lachmi
    2. COHaving re-read your question I've added another paragraph. Hope that helps.
      singulars
      1. PO
      1. USJustABitOfCode
    3. COIn terms of the DB, I decided the best use of my optimization time / cash is to make sure everything is cached. Since the entire DB is about 300MB and growing very slowly, I just added another 2GB of ram and I'm getting very high numbers for foundincache. The main issue now is the construction of the page itself. Since it is made of several usercontrols, rendering takes a large chunk of the request handeling time. p.s. Thank you for taking the time to edit your answer.
      singulars
      1. PO
      1. USElad Lachmi
 

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