On Friday, April 27, 2018 at 11:59:44 PM UTC+3, NS wrote:
> I observed much better write performance with SSD compare to HDD which is 
> kinda expected. Are there any fine-tuningĀ I can do to improve write times for 
> HDD?
> 
> 
> The data is observed using following client code (mostly from 
> influxdb/client's README)
> 
> 
> https://gist.github.com/nileshsimaria/947bc5430ce8754f9992e0a03c8147a7
> 
> 
> SSD
> 
> 
> samples       writes  time
> 500   50      00.43s
> 500   100     00.51s
> 500   150     00.86s
> 500   200     00.98s
> 500   250     01.23s
> 500   300     01.48s
> 
> 
> 
> HDD
> 
> 
> samples       writes  time
> 500   50      02.31s
> 500   100     04.24s
> 500   150     05.92s
> 500   200     08.61s
> 500   250     10.69s
> 500   300     12.58s
> 
> 
> Thanks,
> 
> Nilesh

Well, take a look at http://www.storagesearch.com/ssdmyths-endurance.html for 
once.

I assume you are working with linux, so take a look at 
https://wiki.debian.org/SSDOptimization



We had SSD die on us when we had a cassandra DB on that disk with heavy writes.
took 8 months to reach the write limit on the disks.

it all depends on the amount of writes you have as well as is it Enterprise 
grade SSD vs home grade.

As far as I remember, we had to buy Enterprise grade, and upgrade a patch for 
the RHEL to make sure we don't pitfall again.

Another article you might find usfull : 
https://www.kingston.com/en/ssd/enterprise/best_practices/enterprise_versus_client_ssd

-- 
Remember to include the version number!
--- 
You received this message because you are subscribed to the Google Groups 
"InfluxData" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/influxdb.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/influxdb/961c0f53-c951-470d-87c3-741ba235348e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to