On Jun 20 2016, Brandon <[email protected]> wrote:
> I noticed that mount.s3ql was persisting in taking up a considerable amount
> of CPU during copies, so I had to suspend file copies so other processes
> could use the CPU. I killed the rsync process that was copying files, and
> then fusermount -u'd each of the S3 endpoints that S3QL was using. However,
> I found that ten minutes later, mount.s3ql's python process was still
> running in the background and was not only still taking up large amounts of
> cpu (system load > 10, on a 6-core machine) but it was also still
> exchanging data with Amazon as confirmed by tcpdump and netstat. However,
> lsof did not report any of the files I was copying open by the python
> process.
>
> Any idea what was going on?
It is processing cached data. If you don't want that much dirty data to
accumulate in the cache, reduce the number of cache entries and/or cache
size.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" 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.
