RE: Machine requirements

2003-06-16 Thread Adam Nelson
I suppose you're doing this on your workstation (Windows?)? Ideally, Mysql should be on it's own machine - it (or any database) is designed to suck up resources. Also, you definitely need to tweak the configuration file. MySQL's default config is very anemic (annoying I know) as opposed to Oracl

Re: Machine requirements

2003-06-14 Thread Curtis Maurand
methinks you have other troubles. i've been running MySQL on K6II-266 for a long time and its been running fine serving up several databases with multiple users. 512MB of RAM currently but it had only 128 until recently. Its running Linux (RedHat 7.2). I recently switched to 4.03, but it had b

Re: Machine requirements

2003-06-13 Thread Tom Dangler
What table type is this? If it's MyISAM select count(*) should be instantaneous. If it's InnoDb and you've got a large dataset (say 1 million+) then select count(*) will be slow b/c it doesn't store the # of records in the table, thus it has to count records. MyISAM does store the count so it

Re: Machine requirements

2003-06-13 Thread Becoming Digital
MySQL should have no problems running on your system, and if it runs better on another box, that would indicate a configuration problem or background processes clogging up the works. If you post your my.cnf file, someone here might be able to rule out the former. Edward Dudlik Becoming Digital ww

Re: Machine requirements

2003-06-13 Thread Brent Baisley
I think something is definitely wrong with your setup or your query. A query for a count of the number of rows should be almost instantaneous. How are your querying? You should be using: select count(*) from tablename Any other query that you filter on should have a index on the search field. A