Sponsored Content
Full Discussion: RAID 0 for SSD
Special Forums Hardware Filesystems, Disks and Memory RAID 0 for SSD Post 302779837 by fpmurphy on Wednesday 13th of March 2013 11:54:13 AM
Old 03-13-2013
Hardware RAID0 is always faster than a single disk because you can step the reads and writes across the two disks simultaneously. However, I have never come across a case where throughput was doubled. Typically you will get something like a 50% increase in throughput.

Software RAID0 can provide throughput improvement but typically less than hardware RAID0.
 

8 More Discussions You Might Find Interesting

1. BSD

Using SSD in FreeBSD

Now that SSD drives are becoming mainstream, I had a few questions on installing a SSD drive in a FreeBSD environment. Can FreeBSD be made SSD aware, that is, somehow let FreeBSD know that reads and writes should be limited or deferred to extend the disk's life? Is there a setting for wear... (0 Replies)
Discussion started by: figaro
0 Replies

2. UNIX for Dummies Questions & Answers

RAID software vs hardware RAID

Hi Can someone tell me what are the differences between software and hardware raid ? thx for help. (2 Replies)
Discussion started by: presul
2 Replies

3. AIX

SSD with GPFS ?

Hi, does anyone here happen to know if I could run GLVM or GPFS on Solid State Disks? I have a high volume / high transaction Sybase HACMP cluster currently setup with SRDF to the DR datacentre. My business now considers to move everything to SSD storage but we still need to get the data to... (0 Replies)
Discussion started by: zxmaus
0 Replies

4. AIX

SCSI PCI - X RAID Controller card RAID 5 AIX Disks disappeared

Hello, I have a scsi pci x raid controller card on which I had created a disk array of 3 disks when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk ) suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies

5. Solaris

Software RAID on top of Hardware RAID

Server Model: T5120 with 146G x4 disks. OS: Solaris 10 - installed on c1t0d0. Plan to use software raid (veritas volume mgr) on c1t2d0 disk. After format and label the disk, still not able to detect using vxdiskadm. Question: Should I remove the hardware raid on c1t2d0 first? My... (4 Replies)
Discussion started by: KhawHL
4 Replies

6. Red Hat

RAID Configuration for IBM Serveraid-7k SCSI RAID Controller

Hello, I want to delete a RAID configuration an old server has. Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton? I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Discussion started by: @dagio
0 Replies

7. UNIX for Dummies Questions & Answers

What should I format my SSD with?

Hello All, I recently received a new SSD that I am going to use for the purpose of Booting Virtual Machines. I use VMWare Player to boot Windows Guest Operating Systems onto my Linux Laptop. I currently have a SSD drive that I use for this exact same purpose that is formatted as ext3 and I'm... (3 Replies)
Discussion started by: mrm5102
3 Replies

8. Linux

CentOS 6.6 SSD trim on HP DL380 G2 RAID 0

I'm running glusterfs on CentOS 6.6 two nodes, (the SSD (samsung 840 1TB x2) is RAID 0 on the HP DL380 G6) x2, and trimming is not enable on it by checking /dev/sdb1/xxxxx/discard_max_bytes=0. Do I still need trimming? Somehow my filesystem is fine with 35-30% free space and running very fast. ... (1 Reply)
Discussion started by: itik
1 Replies
Netlogger Throughput Plugin(3)					 globus ftp client				    Netlogger Throughput Plugin(3)

NAME
Netlogger Throughput Plugin - Defines #define GLOBUS_FTP_CLIENT_THROUGHPUT_NL_PLUGIN_MODULE (&globus_i_ftp_client_throughput_nl_plugin_module) Functions globus_result_t globus_ftp_client_throughput_nl_plugin_init (globus_ftp_client_plugin_t *plugin, const char *nl_url, const char *prog_name, const char *opaque_string) globus_result_t globus_ftp_client_throughput_nl_plugin_init_with_handle (globus_ftp_client_plugin_t *plugin, NLhandle *nl_handle, const char *opaque_string) globus_result_t globus_ftp_client_throughput_nl_plugin_destroy (globus_ftp_client_plugin_t *plugin) globus_result_t globus_ftp_client_throughput_nl_plugin_set_callbacks (globus_ftp_client_plugin_t *plugin, globus_ftp_client_throughput_plugin_begin_cb_t begin_cb, globus_ftp_client_throughput_plugin_stripe_cb_t per_stripe_cb, globus_ftp_client_throughput_plugin_total_cb_t total_cb, globus_ftp_client_throughput_plugin_complete_cb_t complete_cb, void *user_specific) Detailed Description This plugin allows a user to easily use the throughput plugin to log performance data vi Netlogger. The plugin will log the following Event Types with its coressponding info TransferPerfTotal : This event type will be sent everytime a throughput plugin total callback is received. o URL.SOURCE <string> Source url of transfer o URL.DEST <string> Dest url of transfer o BYTES <int> Total bytes transfered thus far o BW.CURRENT <float> Current (instantaneous) bandwidth o BW.AVG <float> Average (instantaneous) bandwidth TransferPerfStripe : This event type will be sent everytime a throughput plugin stripe callback is received. o URL.SOURCE <string> Source url of transfer o URL.DEST <string> Dest url of transfer o INDEX <int> The stripe index the event applies to o BYTES <int> Total bytes transfered thus far on this stripe o BW.CURRENT <float> Current (instantaneous) bandwidth on this stripe o BW.AVG <float> Average (instantaneous) bandwidth on this stripe TransferBegin : This event type will be sent everytime a throughput plugin begin callback is received. o URL.SOURCE <string> Source url of transfer o URL.DEST <string> Dest url of transfer TransferEnd : This event type will be sent everytime a throughput plugin complete callback is received. o SUCCESS <bool> Completion status Define Documentation #define GLOBUS_FTP_CLIENT_THROUGHPUT_NL_PLUGIN_MODULE (&globus_i_ftp_client_throughput_nl_plugin_module) Module descriptor. Function Documentation globus_result_t globus_ftp_client_throughput_nl_plugin_init (globus_ftp_client_plugin_t *plugin, const char *nl_url, const char *prog_name, const char *opaque_string) Initialize netlogger wrapped throughput plugin This will initialize a netlogger wrapped throughput plugin. Note that the nl_url may be NULL. Regardless of what nl_host is set to, if the env variable NL_DEST_ENV is set, logging will always occur to that location. Parameters: plugin a plugin to be initialized nl_url the url to log to (May be NULL) Valid urls are: file://tmp/netlog.log x-netlog://host[:port] x-syslog://localhost prog_name This is used as the prog name in the NetLoggerOpen call opaque_string this is an opaque string that will be inserted into all logged statements. (may be NULL) Returns: o Error on NULL plugin or failure to init throughput plugin o Error on NetLogger open o GLOBUS_SUCCESS globus_result_t globus_ftp_client_throughput_nl_plugin_init_with_handle (globus_ftp_client_plugin_t *plugin, NLhandle *nl_handle, const char *opaque_string) Initialize netlogger wrapped throughput plugin This will initialize a netlogger wrapped throughput plugin. Instead of passing a NetLogger url as in the plain init func, you can pass in a previously 'Open'ed NLhandle. This handle will not be destroyed by this plugin. Parameters: plugin a plugin to be initialized nl_handle a previously opened NetLogger handle opaque_string this is an opaque string that will be inserted into all logged statements. (may be NULL) Returns: o Error on NULL plugin or failure to init throughput plugin o Error on NetLogger open o GLOBUS_SUCCESS globus_result_t globus_ftp_client_throughput_nl_plugin_destroy (globus_ftp_client_plugin_t *plugin) Destroy netlogger wrapped throughput plugin Frees up memory associated with plugin. Parameters: plugin plugin previously initialized with init (above) Returns: o GLOBUS_SUCCESS o Error on NULL plugin globus_result_t globus_ftp_client_throughput_nl_plugin_set_callbacks (globus_ftp_client_plugin_t *plugin, globus_ftp_client_throughput_plugin_begin_cb_tbegin_cb, globus_ftp_client_throughput_plugin_stripe_cb_tper_stripe_cb, globus_ftp_client_throughput_plugin_total_cb_ttotal_cb, globus_ftp_client_throughput_plugin_complete_cb_tcomplete_cb, void *user_specific) Receive throughput callbacks You can still get the automatic netlogging of throughput along with receiving the same throughput callbacks that the throughput plugin provides by using this function to set these callbacks. Note that the callbacks are defined the same as in the throughput plugin Parameters: plugin begin_cb the callback to be called upon the start of a transfer per_stripe_cb the callback to be called every time updated throughput info is available for a given stripe total_cb the callback to be called every time updated throughput info is available for any stripe complete_cb the callback to be called to indicate transfer completion user_specific a pointer to some user specific data that will be provided to all callbacks Returns: o Error on NULL or invalid plugin o GLOBUS_SUCCESS See also: Throughput Performance Plugin Author Generated automatically by Doxygen for globus ftp client from the source code. Version 7.3 Mon Apr 30 2012 Netlogger Throughput Plugin(3)
All times are GMT -4. The time now is 11:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy