The first thing you should do is to check that the DB queries you issue are efficient. With Sybase this means setting the SHOWPLAN and STATISTICS IO options, and checking to make sure that all accesses are done via indexes (no table scans for actual physical tables), and that the query plans make sense.

The second thing is to see if the data fetch algorithm can be improved to reduce the amount of work needed to find the appropriate data. DB engines are optimized (and incredibly efficient) at finding data given a set of criteria and proper indexes/joins between tables - making use of that power can improve overall speed by several orders of magnitude (just as dragonchild mentioned above)

Michael

In reply to Re: A profiling surprise ... by mpeppler
in thread A profiling surprise ... by chexmix

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.