On Wed, Jun 26, 2013 at 09:58:36PM +0200, Holger Hans Peter Freyther wrote:
So unless there is an issue with my recording/replay I think that
besides my opinion that mapping a 4MB file 65 times is ugly, it
also appears to be slower for the above workload in journald.
ping? any comments? what
On Fri, Jun 21, 2013 at 06:01:08PM +0200, Holger Hans Peter Freyther wrote:
Do you have an idea on how this could be done?
Hi,
first of all the MMAP cache is not why journald is slow but that is
for another mail/benchmark. I was just curious if the mmap cache is
premature optimization or if it
On Fri, Jun 21, 2013 at 7:50 AM, Holger Freyther hol...@freyther.de wrote:
Good Morning,
I had postponed the adoption of systemd due the excessive CPU usage
of the journald. I am re-evaluating the situation with version 204
right now and I noticed that the (virtual) address space is getting
On Fri, Jun 21, 2013 at 12:29:56PM +0200, Kay Sievers wrote:
What's the problem with using address *space*? Address space is not
used memory, file memory mappings are just how things work in general,
they are cheap and should not really matter.
It is a symptom of inefficiency. If an
On Fri, Jun 21, 2013 at 1:42 PM, Holger Hans Peter Freyther
hol...@freyther.de wrote:
On Fri, Jun 21, 2013 at 12:29:56PM +0200, Kay Sievers wrote:
What's the problem with using address *space*? Address space is not
used memory, file memory mappings are just how things work in general,
they
On Fri, 21.06.13 13:42, Holger Hans Peter Freyther (hol...@freyther.de) wrote:
On Fri, Jun 21, 2013 at 12:29:56PM +0200, Kay Sievers wrote:
What's the problem with using address *space*? Address space is not
used memory, file memory mappings are just how things work in general,
they
On Fri, Jun 21, 2013 at 01:53:23PM +0200, Kay Sievers wrote:
Fragmentation, allocation? I don't think we talk about the same thing here.
... you will figure that out.
Mapping an on-disk file a symptom of inefficiency, you might need to
update your idea of how things work.
I didn't say that
On Fri, Jun 21, 2013 at 03:16:50PM +0200, Holger Hans Peter Freyther wrote:
On Fri, Jun 21, 2013 at 01:53:23PM +0200, Kay Sievers wrote:
Fragmentation, allocation? I don't think we talk about the same thing here.
... you will figure that out.
Mapping an on-disk file a symptom of
On Fri, Jun 21, 2013 at 3:16 PM, Holger Hans Peter Freyther
hol...@freyther.de wrote:
On Fri, Jun 21, 2013 at 01:53:23PM +0200, Kay Sievers wrote:
Fragmentation, allocation? I don't think we talk about the same thing here.
... you will figure that out.
I doubt it, because there is nothing
On Fri, Jun 21, 2013 at 04:19:30PM +0200, Kay Sievers wrote:
I have no idea why you care what the journald process does with its
very own 2+GB of address space, and why it uses 128MB of it.
I care about whether or not journald will work reliable on an
unattended system. And from what I see
'Twas brillig, and Holger Hans Peter Freyther at 21/06/13 16:31 did gyre
and gimble:
On Fri, Jun 21, 2013 at 04:19:30PM +0200, Kay Sievers wrote:
I have no idea why you care what the journald process does with its
very own 2+GB of address space, and why it uses 128MB of it.
I care about
On Fri, 21.06.13 17:31, Holger Hans Peter Freyther (hol...@freyther.de) wrote:
On Fri, Jun 21, 2013 at 04:19:30PM +0200, Kay Sievers wrote:
I have no idea why you care what the journald process does with its
very own 2+GB of address space, and why it uses 128MB of it.
I care about
On Fri, Jun 21, 2013 at 05:31:13PM +0200, Holger Hans Peter Freyther wrote:
I care about whether or not journald will work reliable on an
unattended system. And from what I see there is no limit in the
mmap cache. This means that journald can potentially exhaust the
virtual address space.
On Fri, 21.06.13 17:43, Holger Hans Peter Freyther (hol...@freyther.de) wrote:
On Fri, Jun 21, 2013 at 05:31:13PM +0200, Holger Hans Peter Freyther wrote:
I care about whether or not journald will work reliable on an
unattended system. And from what I see there is no limit in the
mmap
On Fri, Jun 21, 2013 at 02:08:27PM +0200, Lennart Poettering wrote:
That said, the current map sizes are nothing we tuned particularly. If
you can show actal performance benefits I am happy to change them.
Yes, I would be interested in having a performance test for this. Do
you have an idea
On Fri, Jun 21, 2013 at 04:42:41PM +0100, Colin Guthrie wrote:
Did you read Lennart's reply?
Only after responding. ;)
I can also assure you that when there was a bug in this cache window
code about eight months ago it was quite obvious. This was fixed
Good Morning,
I had postponed the adoption of systemd due the excessive CPU usage
of the journald. I am re-evaluating the situation with version 204
right now and I noticed that the (virtual) address space is getting
unusual big.
My journald config configuration is:
[Journal]
17 matches
Mail list logo
