Comment 51 for bug 624510

Revision history for this message
Ming Lei (tom-leiming) wrote : Re: [Bug 624510] Re: Copying To USB Is Very Slow

Hi Axis,

On Sat, Mar 17, 2012 at 1:11 PM, Axis Mann <email address hidden> wrote:
> Hi, I went ahead and applied your kernel changes to my primary lucid
> installation which uses the Intel G41M4-F motherboard that I originally
> had the problem on.  This is the same hardware I first tested your
> changes on except that this time I updated the lucid OS release
> installed on the internal SATA harddrive rather than the test instance
> of Lucid that I installed on the USB drive to pre-test your changes.  I
> didn't see the memory leaks I saw earlier duing the test installation.
> However, I did see some fail messages that I didn't see earlier.  Are
> those normal?  Please see attached.

Looks just some vbox related services return failed. If you can't see such
kind of failures after rebooting, please ignore it simply.

>
> However, on a better note, just as before with the test instance, I now
> see better USB read speeds on my primary Lucid Installation, where I
> originally noticed the slow read speeds.
>
> owner@Pluto:~$ sudo hdparm -tT /dev/sdb
> [sudo] password for owner:
>
> /dev/sdb:
>  Timing cached reads:   2920 MB in  2.00 seconds = 1460.61 MB/sec
>  Timing buffered disk reads:  106 MB in  3.02 seconds =  35.08 MB/sec
> owner@Pluto:~$
>
> I also copied a 4 GB file to and from the external USB hard drive to
> confirm that Nautilus reported read and write speeds of approx 30 MB/s.

Looks it is a good news, but I am still not sure why the commit below
can fix your unlink performance issue.

       commit 004c19682884d4f40000ce1ded53f4a1d0b18206 upstream
       [PATCH] USB: EHCI: go back to using the system clock for QH unlinks

So could you help to install the packages under below link to make sure if
there is the performance issue on your G41M4-F with the packages?

       http://kernel.ubuntu.com/~ming/bugs/624510/lucid-40.87-release/

BTW: I just want to double check if the commit above does fix your issue.

Thanks,
--
Ming Lei