O esteemed saint, when I turn on DBI trace (even at maximum level), the only query I see is the one sent to prepare(), which has placeholders. (Can't execute EXPLAIN on it). But say I fill in those placeholders with string datetimes:

 EXPLAIN SELECT logic_id, since, till FROM COND_dummy               
           WHERE logic_id = 9999
           AND ((since >= '2005-01-01 00:00:00' 
                AND since < '2005-01-01 00:00:01')
             OR (till  >  '2005-01-01 00:00:00' 
                AND till  < '2005-01-01 00:00:01')
             OR ('2005-01-01 00:00:00' >= since 
                 AND '2005-01-01 00:00:01' < till))                   
+   
         LIMIT 1;

[download]

It says that it is using my indexes.

+----+-------------+------------+------+---------------+---------+---------+-------+------+--------------------------+
| id | select_type | table      | type | possible_keys | key     | key_len | ref   | rows | Extra                    |
+----+-------------+------------+------+---------------+---------+---------+-------+------+--------------------------+
|  1 | SIMPLE      | COND_dummy | ref  | PRIMARY,IoV   | PRIMARY |       4 | const |    1 | Using where; Using index |
+----+-------------+------------+------+---------------+---------+---------+-------+------+--------------------------+

And just to test the theory that it has something to do with DATETIME and VARCHARS and conversions at all, I changed the DATETIME columns to INT and ran the script again. Exact same behavior. In fact, somehow, using INTs for the since, till columns made everything slower!

[#insert]         [date time]   [ins/s]
     1000 2005-03-09 10:58:10   649.516
     2000 2005-03-09 10:58:14   287.810
     3000 2005-03-09 10:58:19   212.805
     4000 2005-03-09 10:58:26   136.577
     5000 2005-03-09 10:58:34   118.965
     6000 2005-03-09 10:58:45    94.537
     7000 2005-03-09 10:58:57    84.296
     8000 2005-03-09 10:59:10    74.197
     9000 2005-03-09 10:59:26    64.026
    10000 2005-03-09 10:59:44    54.799

[download]

It is a mystery.

In reply to Re^4: DBI performance problem with MySQL by e2ka
in thread DBI performance problem with MySQL by e2ka

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.