The test was a simple "hdparm" but the build/boot times scaled
accordingly too.
___
arm mailing list
arm@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/arm
On 08/02/2013 06:21 PM, DJ Delorie wrote:
Mbps is not directly relates to IOPS ultimately you could have
16gbps fcp interface but if the storage attached to that is slow
without decent caching etc the performance will still be terrible
The same disk was used for all the usb tests, and had way
> Mbps is not directly relates to IOPS ultimately you could have
> 16gbps fcp interface but if the storage attached to that is slow
> without decent caching etc the performance will still be terrible
The same disk was used for all the usb tests, and had way more
mbytes/sec over eSATA.
The iSCSI
> > The fastest disk I/O on trimslice, based on my testing, is via iSCSI
> > over the ethernet port. It can do gigE (125MByte/sec) where usb/sata
> > on arm seems to be limited to 27 MByte/sec or so (37 MByte/sec on
> > intel i7).
>
> Are you really MB/s rather than IOPS bound?
37 MBytes/sec is
On 08/02/2013 05:38 AM, DJ Delorie wrote:
The fastest disk I/O on trimslice, based on my testing, is via iSCSI
over the ethernet port. It can do gigE (125MByte/sec) where usb/sata
on arm seems to be limited to 27 MByte/sec or so (37 MByte/sec on
intel i7).
Are you really MB/s rather than IOPS
The fastest disk I/O on trimslice, based on my testing, is via iSCSI
over the ethernet port. It can do gigE (125MByte/sec) where usb/sata
on arm seems to be limited to 27 MByte/sec or so (37 MByte/sec on
intel i7).
http://www.delorie.com/arm/trimslice/iscsi.html (old)
__
On 08/01/2013 05:41 PM, Richard W.M. Jones wrote:
On Thu, Aug 01, 2013 at 09:59:47AM -0600, Stephen John Smoogen wrote:
On 1 August 2013 09:53, Peter Robinson wrote:
On Thu, Aug 1, 2013 at 4:48 PM, Stephen John Smoogen wrote:
On 1 August 2013 08:42, Richard W.M. Jones wrote:
I'm now doing
On 1 August 2013 11:38, Peter Robinson wrote:
>>> > Send me your kingdom... there's now a number of ARM devices with PCI-e
>>> > buses, or SATA/NICs plugged directly into the SoC so not hanging off
>>> > crappy USB/SPI/GPIO/i2c buses :-D
>>>
>>> But are the devices Richard has those?
>>
>> The Tri
>> > Send me your kingdom... there's now a number of ARM devices with PCI-e
>> > buses, or SATA/NICs plugged directly into the SoC so not hanging off
>> > crappy USB/SPI/GPIO/i2c buses :-D
>>
>> But are the devices Richard has those?
>
> The Trim Slice *has* a PCI bus (apparently unusual for ARM).
On 08/01/2013 12:41 PM, Richard W.M. Jones wrote:
On Thu, Aug 01, 2013 at 09:59:47AM -0600, Stephen John Smoogen wrote:
On 1 August 2013 09:53, Peter Robinson wrote:
On Thu, Aug 1, 2013 at 4:48 PM, Stephen John Smoogen wrote:
On 1 August 2013 08:42, Richard W.M. Jones wrote:
I know that sev
On Thu, Aug 01, 2013 at 09:59:47AM -0600, Stephen John Smoogen wrote:
> On 1 August 2013 09:53, Peter Robinson wrote:
> > On Thu, Aug 1, 2013 at 4:48 PM, Stephen John Smoogen
> > wrote:
> >> On 1 August 2013 08:42, Richard W.M. Jones wrote:
> >>> I'm now doing quite a lot of compilation on my C
On 1 August 2013 09:53, Peter Robinson wrote:
> On Thu, Aug 1, 2013 at 4:48 PM, Stephen John Smoogen wrote:
>> On 1 August 2013 08:42, Richard W.M. Jones wrote:
>>> I'm now doing quite a lot of compilation on my Chromebook and my Trim
>>> Slice. It's OK, provided that two processes don't try to
On Thu, Aug 1, 2013 at 4:48 PM, Stephen John Smoogen wrote:
> On 1 August 2013 08:42, Richard W.M. Jones wrote:
>> I'm now doing quite a lot of compilation on my Chromebook and my Trim
>> Slice. It's OK, provided that two processes don't try to hit the disk
>> at the same time, at which point ev
On 1 August 2013 08:42, Richard W.M. Jones wrote:
> I'm now doing quite a lot of compilation on my Chromebook and my Trim
> Slice. It's OK, provided that two processes don't try to hit the disk
> at the same time, at which point everything grinds to a halt.
>
I know that several ARMS talk to dis
On 08/01/2013 03:42 PM, Richard W.M. Jones wrote:
I'm now doing quite a lot of compilation on my Chromebook and my Trim
Slice. It's OK, provided that two processes don't try to hit the disk
at the same time, at which point everything grinds to a halt.
I'm using cheap SanDisk cards in both (not
On Thu, Aug 01, 2013 at 03:42:53PM +0100, Richard W.M. Jones wrote:
> I'm now doing quite a lot of compilation on my Chromebook and my Trim
> Slice. It's OK, provided that two processes don't try to hit the disk
> at the same time, at which point everything grinds to a halt.
>
> I'm using cheap S
I'm now doing quite a lot of compilation on my Chromebook and my Trim
Slice. It's OK, provided that two processes don't try to hit the disk
at the same time, at which point everything grinds to a halt.
I'm using cheap SanDisk cards in both (not exactly sure of the model,
but they're the cheapest
On Thu, Aug 1, 2013 at 3:42 PM, Richard W.M. Jones wrote:
> I'm now doing quite a lot of compilation on my Chromebook and my Trim
> Slice. It's OK, provided that two processes don't try to hit the disk
> at the same time, at which point everything grinds to a halt.
>
> I'm using cheap SanDisk car
18 matches
Mail list logo
