Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As @Digbyswift mentioned, having one large HTML file with lots of elements increases the page size, which has an impact the overall load time.</p> <p>For older browsers, the number of elements on the page had a _much_more noticeable effect, but you would have to get in to the 10s of thousands of elements range to start hitting the ceiling.</p> <p>For modern browsers, you don't have as low of an element-count ceiling, so you should be fine there, but again, if you are doing a lot of javascript interaction with the elements, it will slow down less powerful clients, such as mobile devices.</p> <p>The <em>biggest</em> trade off you are dealing with, in my opinion, is that by having one much larger page instead of a bunch of individual calls, you are effectively trading size of a single server response with the number of smaller responses needed. Depending on <em>your specific case</em>, it <em>may</em> be a beneficial overall trade, or it may not.</p> <p>I would say that you need to <em>test</em> the differences it makes and base your decision on that. One thing that will affect this are using compression on the responses (aka. GZip or Deflate).</p> <p>Also, for the "portfolio", you mentioned that there are lots of large images. Personally, I would probably <em>not</em> have the actual <code>&lt;img /&gt;</code> tags in the HTML for that section to prevent the browser from loading all of it initially and instead load the images in <em>as needed</em> by writing the elements in with javascript as those images need to be displayed. There are a number of techniques to do this, any you can add in more smarts around <em>when</em> the images get loaded, but reducing those large server calls will speed up the page a great deal. Likely even to the point that having one massive HTML page <em>won't</em> be a performance hit and will likely make it faster.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs there a sensible limit to "display:none" preloading?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UScdeszaq
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs there a sensible limit to "display:none" preloading?
      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. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for such an in-depth response. From what you've said I think my hunch was correct and it would be best to load in the portfolio items with AJAX (because of the images), while keeping all of the other items in the original HTML file. I do also like your idea of loading in the images separately for the porfolio items, could well be an option.
      singulars
      1. PO
      1. USAlexKempton
 

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