Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It could be any number of reasons, though I doubt Apache has anything to do with it. Possible reasons include:</p> <ul> <li>unoptimized queries</li> <li>database tables don't have indexes where they are needed</li> <li>your database server hardware is crap</li> <li>your algorithms and choice of data structures are bad</li> <li>you are calling database too many times (requesting data even though it was loaded on previous screen etc..)</li> <li>your database configuration and caching might be wrong</li> <li>your frontend technology might be problematic (JSF is slow compared to JSP)</li> </ul> <p>First thing you should do is figure out how much time per page render is spent querying database, how much on application server. You should also record count how many queries are executed per render (and which ones). Then substract these 2 times from time to load the page on the client side and you get the third time which is time to output the page to the client and to render the page on the browser.</p> <p>If the time spent in the database on a single query is large then use a database profiler to see where DB is performing long table scans and set up indexes there. If the query returns a lot of data but you are using just a bit of it, try writing a more specific query. If your spend a lot of time in DB because of the number of queries try to reduce the number of queries by caching or reusing data on application server. If time spent of application server seems to be the problem you might need to rethink your algorithms and design choices.</p> <p>If a lot of time is spent in the third part - transferring and rendering it on a client, try optimizing javascript, using expiration headers on your static content, CDNs, etc... Download and install YSlow pluging and use it to test your page and follow its suggestions.</p>
    singulars
    1. This table or related slice is empty.
    1. POjava Saas Product is very slow
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USU Mad
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POjava Saas Product is very slow
      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
    1. This table or related slice is empty.
 

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