SageTV Community  

Go Back   SageTV Community > Hardware Support > Hardware Support
Forum Rules FAQs Community Downloads Today's Posts Search

Notices

Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 03-30-2011, 01:33 PM
pthomas745 pthomas745 is offline
Sage User
 
Join Date: Jun 2008
Posts: 27
New hard drive and 64k blocks

Dead hard drive, new install of Sage. I use an HD-200 plugged into the server. I have a really simple setup, just mostly watch and record TV with two Hauppauge 1650's. No comskip, just a couple of the nicer interface plugins.

The old hard drive was a 500MB SATA. One smaller partition for the XP Pro, and a large partition for Sage recordings.

This time, I'll install two hard drives.

Does Sage still recommend 64K block size in recording drives? I read the Sage Manual (V7) for this and compared it to V6 of the manual, and 64k block sizes aren't mentioned. Since hard drive space is so cheap these days, is 64K just a good way to go to help Sage handle recordings and playback?

And, should the drive with the OS also be formatted in 64K blocks?

Last edited by pthomas745; 03-30-2011 at 01:36 PM.
Reply With Quote
  #2  
Old 03-30-2011, 01:47 PM
GKusnick's Avatar
GKusnick GKusnick is offline
SageTVaholic
 
Join Date: Dec 2005
Posts: 5,083
It's a video buffering issue. 64K blocks were recommended in V6 and earlier to ensure that there was always enough video buffered to cover the seek time between blocks. V7 handles buffering better so that 64K blocks aren't needed anymore.

You definitely do not want to format your OS drive in 64K blocks, since that will result in a lot of wasted space for smaller files. Yes, disk space is cheap, but wasted space reduces disk performance by spreading out the useful data over a bigger area of the disk instead of keeping it all close together.
__________________
-- Greg
Reply With Quote
  #3  
Old 03-30-2011, 02:06 PM
Audacity Audacity is offline
Sage Advanced User
 
Join Date: Mar 2011
Location: Edmonton, AB, Canada
Posts: 91
Quote:
Originally Posted by GKusnick View Post
It's a video buffering issue. 64K blocks were recommended in V6 and earlier to ensure that there was always enough video buffered to cover the seek time between blocks. V7 handles buffering better so that 64K blocks aren't needed anymore
Maybe those Tips and Tricks should be updated if the 64k cluster thing isn't going to help video playback performance.
Reply With Quote
  #4  
Old 03-30-2011, 04:42 PM
pthomas745 pthomas745 is offline
Sage User
 
Join Date: Jun 2008
Posts: 27
Thank you so much for the quick response.

Sage Forums are the best...because there are so many experts here.

Ok....I'm off to rebuild my server.....Having withdrawals from having to watch live TV without Sage!!!
Reply With Quote
  #5  
Old 03-30-2011, 06:21 PM
Beefcake550 Beefcake550 is offline
Sage Expert
 
Join Date: Oct 2004
Posts: 706
I still recommend formatting the sagetv drive to 64k clusters.....it just makes sense.
Reply With Quote
  #6  
Old 03-30-2011, 07:33 PM
MattHelm MattHelm is offline
Sage Icon
 
Join Date: Jun 2005
Location: Chicago, IL
Posts: 1,209
Quote:
Originally Posted by Beefcake550 View Post
I still recommend formatting the sagetv drive to 64k clusters.....it just makes sense.
Me too.
__________________
Server #1= AMD A10-5800, 8G RAM, F2A85-M PRO, 12TB, HDHomerun Prime, HDHR, Colossus (Playback - HD-200)
Server #2= AMD X2 3800+, 2G RAM, M2NPV-VM, 2TB, 3x HDHR OTA (Playback - HD-200)
Reply With Quote
  #7  
Old 03-30-2011, 08:33 PM
stevech stevech is offline
Sage Icon
 
Join Date: Dec 2005
Posts: 1,643
I don't get why the 64KB recommendation is withdrawn. Doesn't this simply reduce the number of Windows NTFS I/Os required? And thus much less overhead? Though Windows may do larger buffering and read-ahead, getting the data from buffers to the application (Sage) in 4KB chunks seems inefficient.
Reply With Quote
  #8  
Old 03-30-2011, 10:42 PM
GKusnick's Avatar
GKusnick GKusnick is offline
SageTVaholic
 
Join Date: Dec 2005
Posts: 5,083
Allocation block size and I/O buffer size are two different concepts. Just because the block size is 4K doesn't mean the OS can't transfer larger units if they happen to be consecutive. What changed in V7 is that it does a better job of allocating consecutively for small block sizes.
__________________
-- Greg
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
7.1.5 & BD From Hard Drive Polypro SageTV Beta Test Software 4 03-27-2011 07:18 PM
2TB Hard Drive wrems Hardware Support 35 06-02-2010 11:57 AM
New Hard Drive viperdiablo Hardware Support 1 02-15-2010 11:33 PM
Recording drive question (calling all hard drive experts!) Kirby Hardware Support 4 07-17-2006 12:01 PM
Which hard drive to use? cpals Hardware Support 2 06-08-2005 02:21 PM


All times are GMT -6. The time now is 11:22 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.