Mark: Once of the great things about MySQL is the prompt attention and response on this list. Thanks for replying to this email so quickly. Read on...
--- Mark Matthews <[EMAIL PROTECTED]> wrote: > j.random.programmer wrote: > > Hi: > > > > Thought I'd mention this (using the latest dev > > J/connect): > > > > A) > > DatabaseMetaData.getColumns() does not return the > last > > > > 4 columns (SCOPE_*) but it should according to the > > > API spec > > I'll look into fixing this right away. You should > write Sun as well, as > their JDBC compliance testsuite doesn't look for > this :( It's kind of a moot point anyway because those SCOPE_* columns don't really do anything as far as I can tell. But hey, you may as well be complete. > > > > B) > > InnoDB, on their benchmark page, say that > inserting > > 100,000 rows into the DB is about 5 seconds. > > > > http://www.innodb.com/bench.html > > > > Can you point out where it says this? When I look at > the benchmark page, > I see that 100,000 inserts take 25 seconds, which > JDBC can pretty much > match (read on for more). > > Quoted (from the page in question): > > InnoDB MyISAM > ------------------------------------------------------------ > 100 000 inserts 25 s. 40 s. > > 100 000 selects on > primary key 57 s. 58 s. > > 100 000 selects on > secondary key 68 s. 95 s. > ------------------------------------------------------------ > True. I mistakenly mis-remembered this figure. The right figure *is* 25s. > > > > I am finding this to be more like 300-400 seconds. > > Try this: > > I think something is broken with your network, or > your machine, read on > for more.... > ... > I would double-check your network. I just ran your > code here on my > desktop runnin Linux, which is known not to have the > fastest java > support, to my test server (100 mbit private > network), and it takes 30 > seconds, > which is 5 seconds longer than 100,000 inserts using > DBI (which is using > native code to access the database, btw), but is not > long enough for > HotSpot to actually optimize the code, either. > You are right. It looks like some sort of network problem. I tried this on a seperate set of 2 machines both on a different network. The driver was running on a windows 2000 box (dual 1 GB) hitting the mysql box (dual xeon, 1 GB, linux) over a 100 Mbit line. This test now took about 55 seconds. I have a feeling that switching to 4.x would make things even faster, seeing as you are getting 30 seconds with a slower box. Are you using 4.x internally for your testing ? Best regards, --j __________________________________________________ Do you Yahoo!? HotJobs - Search new jobs daily now http://hotjobs.yahoo.com/ --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
