comment on

Like others have pointed out - this is a database issue, not a perl issue.

You need to look at the query plan generated for the delete and each of the select statements to ensure that these are as optimal as possible.

Then you may need to look at the server itself to see if you can tune the User Log Cache, and maybe bind a specific named cache to the database's log using 4k IO (i.e. two pages) as this can improve things as well. You also need to look at the actual disk IO subsystem to ensure that this is properly configured.

Michael

In reply to Re: How can I improve the sql statements applying efficiency by mpeppler
in thread How can I improve the sql statements applying efficiency by littlehorse

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks