Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Laudable goal, but you need to focus on the actual demonstrable performance problems -- not where you 'think' the performance problems are.</p> <p>Spend time in a profiler to find the real issues...then go from there. Otherwise you're just churning code without any way of knowing whether you're making a measurable impact.</p> <p>Even if you had a list of "things to change without measuring system performance" would you really trust them to be right for your circumstance?</p> <p>In your situation I would suggest you spend time building test harnesses/performance instrumentation so you can see where to get the most bang for your buck.</p> <p>EDIT: To address the downvote(s) and sentiment about "I know using a PreparedStatement is faster" -- rather than asking for silver bullets, a better question to ask when faced with this issue is "how should I most productively spend my free time to make things better?" The OP clearly wants to improve the situation -- which is great...but without measuring "where it hurts" he's literally shooting in the dark. Is a PreparedStatement faster? Sure -- but if the real performance gremlin is in some other spot, why spend time 'fixing' the DB code when you could make a REAL impact by going after the actual points-of-pain?</p> <p>One other thing: in a stable system such as the OP is describing, making code changes without good quantifiable justification is often considered bad practice, due to the risks introduced. In such stable systems, the question of risk/reward is for ANY code change must be considered. The risk is significant: many "simple, couldn't break anything" changes have slipped release schedules/introduced major problems. The reward? Uncertain, since you don't actually know if your change was responsible for a performance gain. Hence, we profile to make sure we're improving code which matters.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat should I look for when improving performance in Java?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDarkSquid
    1. USDarkSquid
    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. COBeat me to the punch. Excellent answer.
      singulars
      1. PO
      1. USPaul Sonier
    2. COYes! There's no point in making a piece of code faster if you spend only 0.0000000001% of your time in it.
      singulars
      1. PO
      1. USLaurence Gonsalves
    3. COHmmm. I do not really need to measure the impact of connecting to the database using PreparedStatement. I just know it's faster.
      singulars
      1. PO
      1. USPaulo Guedes
 

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