121 reputation
7
bio website
location Dallas, TX
age 37
visits member for 2 years, 7 months
seen Jul 6 at 16:54

...


Sep
24
awarded  Autobiographer
Sep
12
awarded  Popular Question
Apr
12
awarded  Scholar
Apr
12
accepted InnoDB UPDATE slow need a better option
Apr
11
awarded  Teacher
Apr
11
awarded  Student
Apr
10
answered InnoDB UPDATE slow need a better option
Apr
9
comment InnoDB UPDATE slow need a better option
1) Well it's currently in a test server, but will be production so I don't think I can do that. 2) I thought this was doing a bulk transaction? But my MySQL knowledge is limited. How would I go about changing this to doing bulk transactions? 3)It originally was MyISAM, but the locking when updating caused issues. 4) I would love to get better hardware, but I don't see this taxing the system except for possibly driveIO writes/reads. no CPU/Memory spike with this setup. I don't have access/knowledge how to read the drive read/writes. Just have htop to monitor.
Apr
9
comment InnoDB UPDATE slow need a better option
I did edit my.cnf I've been playing with innodb_buffer_pool_size and inno_log_bugger_size, but not sure what to set them... I've been using the mysqltuner.pl script from mysqltuner.pl I cannot delete the import table as other tables look for data from it. But I'm thinking of importing to a temp table and then finding the differences VS setting a deleteme option. But this is over my MySQL comfort zone.
Apr
9
revised InnoDB UPDATE slow need a better option
added 63 characters in body
Apr
8
awarded  Editor
Apr
8
revised InnoDB UPDATE slow need a better option
Changed the way I asked the question.
Apr
7
comment InnoDB UPDATE slow need a better option
deleteme is not a primary key or linked to any other table. It's used as a marker to mark rows that need deleted before they are updated, and the ones that are left with deleteme = 1 are removed. basic demo version of the table setup sqlfiddle.com/#!2/9604b/2
Apr
7
asked InnoDB UPDATE slow need a better option
Apr
7
awarded  Supporter