News:

Buffalo provides Data Recovery services. Read about it here.

Main Menu

secure lock ware affecting speed?

Started by jho, April 12, 2009, 05:48:32 PM

Previous topic - Next topic

jho

   

HD-CE1.0TU2  I first was getting reading from Fat32 out of the box about 30mb/s   writing a little slower.

After using secure lock 256bit encryption, the drive only reads and write at about 15mb/s.

I think there is alot of overhead dealing with encryption, I noticed the CPU usage goes up alot during it.

 

Can you confirm this is normal?  Would the secure lock ware run faster if I choose only 128bit encryption instead of 256bit?

 

 


Dustrega

This is normal as the data is being encrypted to the drive as it is written. You might get a higher performance running 128-bit vs. 256-bit but beware if you change the encryption you'll have to reformat your drive.

jho

   

Thanks, I did try 128 bit and the transfer rate is about 20 MB/S which is a bit faster, when first unlocking the drive it is faster too.  CPU usage is less.  I also think the transfer rate would be faster on a computer CPU.

 

 


jho

   

Hi, can you confirm if Buffalo is working on a Vista 64 bit version of secure lock ware.

 

for example if I encrypt the drive using secure lock ware today.

 

If a 64 bit version is released for Vista 64 bit,  I will still be able to decrypt the drive without formating right?

 

 


jho

   

Sorry, one more question.. am I required to use NTFS when using secure lock ware?  Can I use

FAT32?

 


Dustrega

Drive encryption won't work on FAT32 I don't believe.

Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 200 (show)
Files included: 35 - 1354KB. (show)
Memory used: 968KB.
Tokens: post-login.
Queries used: 15.

[Show Queries]