RE: mySql versus Sql Server performance

Sorry, that should be 200MB not 20MB (still doesn't seem like much to me) Patrick myList - everything you could possibly want (to buy) -Original Message- From: Patrick Thompson Sent: Monday, October 25, 2010 5:24 PM To: 'Gavin Towey'; mysql@lists.mysql.com Subject: RE: mySql versus Sql

RE: mySql versus Sql Server performance

Here's the innodb stuff - although the largest data set I've used in the stats run is around 20MB, which doesn't seem like much to me. 'innodb_adaptive_hash_index', 'ON' 'innodb_additional_mem_pool_size', '2097152' 'innodb_autoextend_increment', '8' 'innodb_autoinc_lock_mode', '1' 'innodb_buffer

RE: Load Data Infile Errors

The answer is 3 =) With myisam tables, you can have partially complete statements. That is if you get an error, all rows handled before the error are still in the table. With innodb, an error generates a rollback and your table is returned to its state before the statement was run. To find t

RE: Is SSD suitable for mysql server?

> I guess it depends on how important your data is too. Quite > a few of the SSDs on the market have been proven to not > honour flush requests, so if the power goes out you've got > corrupted data. Uh. If you're not using a UPS battery backup then you deserve to loose your data. And if you do

RE: mySql versus Sql Server performance

So it's a primary key lookup. That's a rather large primary key though, it's going to bloat the table size since innodb in mysql uses clustered indexes. So the explain plan and table structure look pretty straightforward. It is using the index to satisfy the query. The next question is what d

RE: [SPAM] RE: mySql versus Sql Server performance

Thanks Martin, though I'm somewhat confused by your message - there are no joins in the query (unless the longtext s thought of that way) and the Explain seems to indicate the query is using the ItemsById primary index (which is what I would expect). Patrick myList - eve

Load Data Infile Errors

Hello, I have a question about the execution cycle of LOAD DATA INFILE. If I issue a large file via LDI LOCAL, I know that the file is copied to the MySQL server and executed there. But at what point does the statement finish from the sender's point of view? 1) When the file is successfully c

RE: mySql versus Sql Server performance

Query: SELECT * FROM Item WHERE CollectionID = 'a0d3937b-f5a8-0640-dec8-bdd60f7f4775' AND ExternalID = 'fred1' Explain Extended: select '17304' AS `ID`,'fred1' AS `ExternalID`,'a0d3937b-f5a8-0640-dec8-bdd60f7f4775' AS `CollectionID`,NULL AS `ItemTypeVersion`,'http://cipl.codep

Re: Is SSD suitable for mysql server?

On 10/25/2010 4:32 AM, Glyn Astill wrote: There have been some reports of raid cards not behaving themselvs with SSDs attached. I'd be surprised if these bugs haven't all been worked out by now. SSDs started to hit the mass market in force about two years ago. Any vendor still shipping a d

Re: Is SSD suitable for mysql server?

On 10/25/2010 3:03 AM, Johan De Meersman wrote: SSD may still be useful if you have a lot of writes, though. Only if by "a lot" you mean "a minority". A lone 2 TB rotating disk will beat a top-of-the-line SSD for linear writes, and you can beat an SSD for linear reads with a pair of disks in

Re: Query precision issue

Sairam, sorry to be so blunt, and please don't feel offended: Sairam Krishnamurthy wrote: > [[...]] > > Can somebody help me to find out the problem? I can very well truncate > the trailing zeros when querying, but I am interested in finding why an > additional trailing zero returns an empty se

Re: Query precision issue

That is exactly the problem. It is float. Thanks for your input. Thanks, Sairam Krishnamurthy +1 612 859 8161 On 10/25/2010 01:00 PM, Dan Nelson wrote: In the last episode (Oct 25), Sairam Krishnamurthy said: I have simple query like 'select * from table1 where column1=-107.689878'.

Re: Query precision issue

In the last episode (Oct 25), Sairam Krishnamurthy said: > I have simple query like 'select * from table1 where > column1=-107.689878'. This returns an empty set. But there is data > corresponding to this value of column. > > When I looked more into it, it seems like a precision issue. The

RE: mySql versus Sql Server performance

MySQL and most other databases require adjustment of server settings, and especially of table structures and indexes to achieve the best performance possible. If you haven't examined index usage for the queries you're running, or adjusted server memory settings from defaults, then it's no surpr

Re: Query precision issue

Thats because float columns store approximate data values, you may need to use an error range in comparison, or at your own discretion use the decimal data type. You can get more info in: http://dev.mysql.com/doc/refman/5.1/en/numeric-types.html http://dev.mysql.com/doc/refman/5.1/en/problems-

Query precision issue

All, I have simple query like 'select * from table1 where column1=-107.689878'. This returns an empty set. But there is data corresponding to this value of column. When I looked more into it, it seems like a precision issue. The value for column1 is -107.689878. More interesting is tha

RE: mySql versus Sql Server performance

That's true for the deletes - but not for save and get. The ddl is available here http://cipl.codeplex.com/SourceControl/changeset/view/2460#57689 The code that accesses it is here http://cipl.codeplex.com/SourceControl/changeset/view/2460#57729 Patrick myList - everyth

Re: mySql versus Sql Server performance

I merely skimmed it, but your comment that you pay the query compilation cost on every request suggests to me that you're not using prepared statements. If you can, you should :-) Also, MySQL *does* support SPs, from 5.0 onwards or something. You could split into separate modules for pre- and post

mySql versus Sql Server performance

I am running an open source project that provides an abstraction layer over a number of different stores. I am puzzled by performance numbers I am seeing between mysql and sql server - a brief discussion is available here http://cipl.codeplex.com/wikipage?title=Data%20Provider%20Comparison The

Re: Is SSD suitable for mysql server?

--- On Mon, 25/10/10, Johan De Meersman wrote: > From: Johan De Meersman > Subject: Re: Is SSD suitable for mysql server? > To: "wroxdb" > Cc: "mysql" > Date: Monday, 25 October, 2010, 10:03 > On Mon, Oct 25, 2010 at 7:56 AM, > wroxdb > wrote: > > > Hello, > > > > We are a company for gaming

Re: Is SSD suitable for mysql server?

On Mon, Oct 25, 2010 at 7:56 AM, wroxdb wrote: > Hello, > > We are a company for gaming. > Our main db is mysql 5.1 installed on Linux. > Currently the hardware for mysql is 2*4 CPU, 16G memory, Raid 10 (four > disks). > Now we have the plan to replace the disks with SSD for better performance. >

Re: WTA Increasing InnoDB Speed

On Mon, Oct 25, 2010 at 6:25 AM, mos wrote: > At 06:12 AM 10/24/2010, you wrote: > >> Regardless of that, it would be nice to know what the parameters are that >> cause this slowdown - some people may be stuck with the default version - >> companies with a support contract come to mind. >> > > Yo