On 23 January 2018 at 23:50, linux guy <linuxguy...@gmail.com> wrote:
> Update.
>
> The dnf update process is still very, very slow on the RPi3.  It will take
> all night (8 hours) to run.   For comparison, I installed F27 workstation on
> a Celeron N3000 machine with 2 GB of RAM and a 128 GB SSD earlier this week.
> A much larger (workstation versus minimal server) dnf update took in the
> order of 10 minutes on that machine.  I don't think the I/0 speed and
> processing power difference is an order of 1000 between these two machines.
>
> I ran $top in another console while #dnf update was running.   dnf is rarely
> at the top of the top listing.  And when it is, it is using ~40% of the CPU
> and only 12% of the memory.  None of the swap memory is being used at all.
> 90% of the time $top itself is the largest resource user.

That would say it is not anything to do with the CPU and something to
do with the IO. The first thing I would look at is that the Kingston
card may have been bootlegged or it is shoddy. There were a large
number of fake cards out there where someone relabeled lower quality
ones to higher ones. The second is that the speed of IO is going to be
peak read/write rates and not average rates. This means that some
manufacturer cards will be rated as EV10 but only when they are
running downhill with the wind to their back (as they would say about
cars).

Finally the connector to the rasp pi to the MMC may be dirty. The old
clean with alchohol and such have helped on other models for other
people. That said, MMC is slow. It is not as fast as SSD in any shape
or form so that even an old slower celeron is going to smoke the
raspberry pi nearly every time.



-- 
Stephen J Smoogen.
_______________________________________________
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

Reply via email to