Hi Dirk,

On 2014-03-08 at 11:32, Dirk-Jan C. Binnema wrote:
> ,----
> | % sudo hdparm -Tt /dev/sda
> |  
> | /dev/sda:
> |  Timing cached reads:   24630 MB in  2.00 seconds = 12332.61 MB/sec
> |  Timing buffered disk reads: 356 MB in  3.01 seconds = 118.46 MB/sec
> `----

OS X doesn't have hdparm and from a quick google nothing similar. I
created a 10 GB file and read it to test the read speed. Perhaps this
is a similar metric?

== WRITE == 
$ time dd if=/dev/zero bs=1024k of=tstfile count=10240
10240+0 records in
10240+0 records out
10737418240 bytes transferred in 61.309395 secs (175134957 bytes/sec)

real    1m1.422s
user    0m0.033s
sys     0m12.739s

== READ ==
$ time dd if=tstfile bs=1024k of=/dev/null count=10240
10240+0 records in
10240+0 records out
10737418240 bytes transferred in 49.813230 secs (215553543 bytes/sec)

real    0m49.831s
user    0m0.030s
sys     0m8.964s

That read speed of 215553543 bytes/sec is 205 MB/s, which seems
comparable to your buffered (non-cached?) read.

>> Searching is also much slower than Dirk's earlier report, although I don't 
>> mind waiting a few seconds for a search:
>>
>> $ time mu find hello |wc -l
>>     2555
>> real    0m1.031s
>> user    0m0.165s
>> sys     0m0.287s
>>
>
> My times are a bit better (with about half the amount of message):
>
> ,----
> | % time mu find hello | wc -l
> | 2105
> | 0.03s user 0.02s system 98% cpu 0.057 total
> `----

That isn't "a bit better"! That is a LOT better. But again, the search
speed isn't as much of an issue as the index speed.


> I have a Macbook lying around, and when I have some time, I'll
> happily work on this... but I am quite busy with other stuff
> (obviously I'm waiting for Google or Facebook to buy mu4e for a few
> $10E9 :)
>
> In other words, there's an interesting task waiting for some
> MacOS-based hacker -- some profiles (such as what Linux' perf tool
> produces) would be a great start.

Unfortunately I am probably not that hacker. I just looked around a
bit, and under XCode main menu there is an option for "Open Developer
Tool > Instruments". In the Instruments app it looks like I can attach
a monitor to a process or a program and trace / profile it
(OSX>FileSystem>FileActivity). I did so briefly with mu and see lots
of info, but I'm rapidly out of my depth. Screen-shot of the
Instruments.app is here:
http://dl.getdropbox.com/u/12453163/profile.png 

Anyway... I'll keep trying to use mu4e. Perhaps the speed improvements
offered by the SSD will be enough. If not, I'll wait for said hacker
to help out...

Thanks,

  -k.

-- 
You received this message because you are subscribed to the Google Groups 
"mu-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to