Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Linux operating system (OS), a U...  <--  <--- Return to Home Page
   Networked Database  Linux operating system (OS), a U...   [723 / 900] RSS
 From   To   Subject   Date/Time 
Message   Maurice Kinal    Benny Pedersen   JMS567 SATA 6Gb/s bridge & 64G msata TS64GMSA 370   February 21, 2019
 9:57 PM *  

Hej Benny!

Cutting and pasting for stats;

# writing to onboard uSD card using dd
  dd if=/dev/zero of=test.dd bs=1M count=512
  512+0 records in
  512+0 records out
  536870912 bytes (537 MB, 512 MiB) copied, 58.4449 s, 9.2 MB/s

# writing to usb connected msata using dd
  dd if=/dev/zero of=test.dd bs=1M count=512
  512+0 records in
  512+0 records out
  536870912 bytes (537 MB, 512 MiB) copied, 12.8056 s, 41.9 MB/s

# writing to usb connected 2.5" laptop drive using dd
  dd if=/dev/zero of=test.dd bs=1M count=512
  512+0 records in
  512+0 records out
  536870912 bytes (537 MB, 512 MiB) copied, 12.9187 s, 41.6 MB/s

Both the msata and the 2.5" laptop drive are 4 times faster than the uSD. 
However it should be noted that there is an issue with the usb sata bridge that
 states;

[  139.399549] usb 1-1.2: The driver for the USB controller dwc_otg_hcd does
not support scatter-gather which is
[  139.399569] usb 1-1.2: required by the UAS driver. Please try an other USB
controller if you wish to use UAS.

However it wasn't fatal as demonstrated by the dd write to the drive mounted on
 the JMS567 SATA 6Gb/s bridge, but after witnessing this I will continue to use
 the 2.5" laptop drive given that there are no such errors on there and the
results were just as good.  Hopefully newer raspberry pi's will ditch the uSD
interface and put on a msata or m.2 controller/interface in the future.  uSD's
should be left to crippled hardware as people who use those devices don't seem
to mind (over)paying for utter crap.  ;-)

I won't even mention the onboard wifi.  More useless crap that is a drain on
the system.  :::sigh:::

Anyhow, for the record, the same test on a usb3.0 interface;

# writing to usb3 connected msata using dd
  dd if=/dev/zero of=test.dd bs=1M count=512
  512+0 records in
  512+0 records out
  536870912 bytes (537 MB, 512 MiB) copied, 1.13874 s, 471 MB/s

MUCH BETTER!!!  :-)

Hopefully you'll have better results with the addon card.  One thing for sure
is that msata is a vast improvement over the onboard uSD and is worth the extra
 investment.

Livet er godt,
Maurice

... En M├╕├╕se slog engang min s├╕ster ...
--- GNU bash, version 5.0.2(1)-release (aarch64-raspi3b+-linux-gnu)
 * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Linux operating system (OS), a U...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0957 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_pkmgvhihg7hs2qjbtkato0d3j4, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_pkmgvhihg7hs2qjbtkato0d3j4, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_pkmgvhihg7hs2qjbtkato0d3j4, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0