ssd

Is there a reliable, quick, deterministic way (i.e. not a benchmark) to check whether the system drive Mac OS X is on is a Solid State Drive? Is there any other indicator how well disk handles parallel access? I'm trying to adjust number of threads that my program is going to use for disk-bound operations. I'm not interested in raw speed or seek time, only which type of access – serial or parallel – is faster for the drive. I don't expect users of my program to use iSCSI or RAID. SSD is my focus, anything else is nice-to-have. Device Characteristics of IOAHCIBlockStorageDevice contains this

In the following EC2 instance types which have SSD drives r3.2xlarge r3.4xlarge i2.xlarge When I login through SSH, I am unable to see the SSD drives. I was trying "df -h". I have tried reboot, but that did not help. tried to terminate and create a new instance that also does not help. Suggesting that its not one-off issue. sandeepkunkunuru I found one solution by trying the steps suggested for adding EBS volumes to Ubuntu instnaces Below are my steps: sudo mkfs.ext4 /dev/xvdb sudo mkdir -m 000 /mnt # isnt required if /mnt exists. echo "/dev/xvdb /mnt auto noatime 0 0" | sudo tee -a /etc/fstab

We are working on a SSD-backed key-value solution with the following properties: Throughput: 10000 TPS; 50/50 puts/gets; Latency: 1ms average, 99.9th percentile 10ms Data volume: ~1 billion values, ~150 bytes each; 64-bit keys; random access, 20% of data fits RAM We tried KyotoCabinet, LevelDB, and RethinkDB on commodity SSDs, with different Linux IO schedulers, ext3/xfs file systems; made a number of tests using Rebench ; and found that in all cases: Read-only throughput/latency are very good Write/update-only throughout is moderate, but there are many high-latency outliers Mixed read/write

I would like to change the performance and behaviour of my C++ application, according to whether the system drive is an SSD or not. Example: With SSD, I want my gameserver application to load each map fully, with all objects in order to maximize performance. With HDD, I want my gameserver application to load only the essential objects and entities in each map, with no external objects loaded. I've seen http://msdn.microsoft.com/en-gb/library/windows/desktop/aa364939(v=vs.85).aspx , which is a way of determining if a certain drive is a HDD, CD ROM, DVD ROM, Removable Media, etc, but it STILL

What is the difference between sequential write and random write in case of :- 1)Disk based systems 2)SSD [Flash Device ] based systems When the application writes something and the information/data needs to be modified on the disk then how do we know whether it is a sequential write or a random write.As till this point a write cannot be distinguished as "sequential" or "random".The write is just buffered and then applied to the disk when we will flush the buffer. Please correct me if I am wrong. When people talk about sequential vs random writes to a file, they're generally drawing a

// if the 'id' variable is not set in the URL, we must be creating a new record else { // if the form's submit button is clicked, we need to process the form if (isset($_POST['submit'])) { // get the form data $mtcn = htmlentities($_POST['mtcn'], ENT_QUOTES); $amount = htmlentities($_POST['amount'], ENT_QUOTES); $currency = htmlentities($_POST['currency'], ENT_QUOTES); $sender_name = htmlentities($_POST['sender_name'], ENT_QUOTES); $sender_country = htmlentities($_POST['sender_country'], ENT_QUOTES); $receiver_name = htmlentities($_POST['receiver_name'], ENT_QUOTES); $comment = htmlentities($

I'm getting ready to release a tool that is only effective with regular hard drives, not SSD (solid state drive). In fact, it shouldn't be used with SSD's because it will result in a lot of read/writes with no real effectiveness. Anyone knows of a way of detecting if a given drive is solid-state? Detecting SSDs is not as impossible as dseifert makes out. There is already some progress in linux's libata ( http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-04/msg03625.html ), though it doesn't seem user-ready yet. And I definitely understand why this needs to be done. It's basically the