Author Topic: preset one Thread for each drive  (Read 2170 times)

Offline dasmarx

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
preset one Thread for each drive
« on: October 23, 2012, 11:44:31 am »
I don't know if this is the right way to call it but i will try to be as clear as possible about what i noticed and how i managed to get this working.

Situation:

Server with Flexraid with 24 Drives. It will spin down the disks after a specific time of no usage.
At least 2 PCs which will access the Servers Flexraid folder.

1. PC 1 will start a movie for some time, lets say 10 Minutes.
2. In the meantime, the not used 23 drives will go to sleep.
3. PC 2 will try to access as many files as possible, like browsing the whole Flexraid drive.
4. PC 1 will get a timeout while still watching the movie.

Way to avoid this:

Set Threads to n+1 disk, where n is the number of disks.

The following is only something i assume:
Is it right, that FlexRaid will try to open a folder for each disk with a Thread? If yes, is this limited to 1 Thread per drive? What will happen if 5 Threads are set and 5 drives need to spin up, will the first started movie stream be queued?


Thanks for any tips on this.

I made some logs with Trace enabled. in the first log, i was watching Hangover until i got a timeout.
In the second log i tried hangover 2 and got no timeout.

https://www.dropbox.com/s/xwii2aztwxxqcxh/1stLogs.rar
https://www.dropbox.com/s/0rzlscqfjsiwl2c/2ndLogs.rar
« Last Edit: October 23, 2012, 11:47:44 am by dasmarx »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: preset one Thread for each drive
« Reply #1 on: October 23, 2012, 01:10:59 pm »
Why are you using the old driver?

Offline dasmarx

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
Re: preset one Thread for each drive
« Reply #2 on: October 23, 2012, 01:42:07 pm »
If this might help, i could change to newer driver, but i had better throughput with old driver.

I will redo the the same test with logs with the new driver. My only goal here is to help you make your product better.


Well, i am very pleased to say that i was not abled to get any timeout with the new driver.
So my tipp would be to use the new driver.
« Last Edit: October 23, 2012, 02:14:45 pm by dasmarx »

Offline Brahim

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8,547
  • Karma: +204/-16
    • View Profile
Re: preset one Thread for each drive
« Reply #3 on: October 23, 2012, 02:50:13 pm »
Now, with the old driver, did you test with the thread count set to N+1?

Note, my asking about why you would use the old driver was not a criticism. I was just curious.
Use which ever driver works best for you (although, most should stick with the new driver).
Basically, use the old driver implementation only if you are sure it works best for you.

Offline dasmarx

  • Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
    • View Profile
Re: preset one Thread for each drive
« Reply #4 on: October 24, 2012, 12:15:51 am »
If i remember right, i was using the old driver because befor switching to Snapshot, i tried Realtime and the old driver was (at that time) more solid. Most likely, i just forgot about switching the drivers.
The 2nd log is with the old driver with n+1 enabled at which i had no timeout even with the old driver.