>
>Hi,
>
>Here is what I understand:
>your queries are already very optimized, you have already played
>with database scheme and application optimisations so there is little
>chance to find any gain there.
>Your setup seems to be right according to disc I/O and RAM since
>all indexes fit in RAM an
Aaron Williams wrote :
>
> > Joseph Bueno wrote:
> >
> >Hi,
> >
> >If you run a single query, MySQL will use only one processor.
> >MySQL multithreading allows you to run multiple queries in parallel,
> >one query per thread.
>
> Right, that I understand. Even while running up to 30 queries it
> Joseph Bueno wrote:
>
>Hi,
>
>If you run a single query, MySQL will use only one processor.
>MySQL multithreading allows you to run multiple queries in parallel,
>one query per thread.
Right, that I understand. Even while running up to 30 queries it pegs the
first CPU at max, and no other CPU
Aaron Williams wrote:
> The tables run upwards of around 13-15 gigs each. The nature of the
> data forces me to search the entire contents (looking for unique
> values) around 3000 times a day. The server is running Solaris 2.8,
Do you have an index on the columns you are querying for unique val
Aaron Williams wrote:
>
> Hello again list. I sent this message yesterday and wasn't able to
> get an answer. Just curious to see if any of the gurus out there care
> to share some insight on a mid-level MySQL setup, and can offer some
> starting points for learning how to troubleshoot the same.
Hello again list. I sent this message yesterday and wasn't able to
get an answer. Just curious to see if any of the gurus out there care
to share some insight on a mid-level MySQL setup, and can offer some
starting points for learning how to troubleshoot the same.
| Begin message:
I have a
