Timeline for Poor SQL performance with raid10
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 21, 2014 at 9:44 | comment | added | Marian | How many rows are we talking about here? As I see your queries they're mostly doing ad-hoc (random) small reads and writes. Don't use the sequential copy perf value as a baseline here, it's useless. Better check the IOPS and random read/write performance of your RAID, that looks far more useful for your workload. Now, why are you doing reads and writes based on Id? Can't you use a set based approach (get 1000 events at once -> insert 1000 items + delete 1000 and then rinse, repeat)? | |
| Jan 21, 2014 at 7:25 | answer | added | Rick James | timeline score: 1 | |
| Jan 19, 2014 at 20:09 | history | migrated | from stackoverflow.com (revisions) | ||
| Jan 19, 2014 at 18:24 | comment | added | AngularAddict | Desktop is on windows and single disk. | |
| Jan 19, 2014 at 16:57 | comment | added | bhttoan | Just to be clear - is your desktop running the same OS and does it have RAID? | |
| Jan 19, 2014 at 15:08 | history | asked | AngularAddict | CC BY-SA 3.0 |