I am not exactly sure what you mean by a plain index, but I am pretty sure that adding a clustering index on a field that is already indexed will not really accomplish anything. I could be confusing myself though.
At this point I think there are two places to looking. First, run the query through whatever explain utilities are available on your DBMS. This may give you some insight into what other optimizations may be useful. This was suggested in a previous post, but may have gotten lost in the shuffle.
The other thing to consider is if you have any sort of hardware limitation. E.g. are you running out of RAM on that machine?
After that, you are going to want to look at if there any database specific options/features you can turn on that may help your query. This type of thing is inherently database specific, and each database usually has a slew of different things you can try. You probably want to find some good perfomance tuning books/references for your database.
I am a DBA neophyte, so I do not really know if your performance requirements of .5s are reasonable. I will say that 30s for that query sounds like a pretty long time to me.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.