All geek questions in one place

The best storage engine for constantly changing data

I currently have an application that uses 130 MySQL tables, all with MyISAM storage engine. Each table has multiple queries every second, including select / insert / update / delete queries, so data and indexes are constantly changing.

The problem I am facing is that the hard drive is unable to handle a wait time of up to 6+ seconds for I / O access with as many read / write operations that MySQL performs.

I thought about moving to one table and making it based on memory. I have never used a memory table for something with so many queries, so I wonder if anyone can give me feedback on whether this will be done correctly?

+1
source share
4 answers

Now I have changed to the MEMORY table, and everything is much better. In fact, I now have additional backup resources on the server, which allows me to continue the expansion of operations.

+1
source

, , - 6 CRUD, . , ( ) ArsDigita 30 Sun Ultra 2 (IIRC) . .

  • ? - , .

  • ? - (, , , ).

  • , InnoDB .

  • . , .

: . . , , , . , , (.. ), .

+2

Is there a specific reason why you are not using innodb? This can lead to performance improvements due to caching and another concurrency model. This will probably require more customization, but can give much better results.

should-you-move-from-myisam-to-innodb

0
source

I think your database structure is very wrong and needs to be optimized, has nothing to do with storage

0
source

Source: https://habr.com/ru/post/1722419/

More articles:


All Articles