[systemd-devel] Hosting a sprint in SF?

[Lennart Poettering]

On Fri, 29.06.12 14:23, Kok, Auke-jan H (auke-jan.h.kok at intel.com) wrote:

> 
> On Thu, Jun 28, 2012 at 4:06 PM, David Strauss <david at davidstrauss.net> wrote:
> > My company just moved into a new office at California and Grant
> > (Chinatown, near the Financial District) in San Francisco -- finally
> > with enough space to host a sprint. We use systemd extensively (100+
> > production Fedora instances) and would like to host a sprint at our
> > office. My personal goal is "journald everywhere," but I would be
> > happy to see better systemd support in other areas.
> >
> > I can almost certainly sponsor travel for some people with a history
> > of contributing to systemd/low-level Linux or projects/languages we'd
> > like to support.
> >
> > Namely, it would be great to work on the following:
> >
> >  * journald logging libraries for every major language. Python and PHP
> > are deep into being kicked off. Java, Ruby, and node.js are next on my
> > list.
> >  * Once a language has journald support, build application-level
> > integration. For example, Drupal's watchdog could go field-for-field
> > into journald. Jenkins could have a plugin for build and
> > administration logs. Twisted's log facility could send to journald.
> >  * Tools to automatically ship journald logs off to systems like
> > Graylog2 and Flume. This is possible now in the
> > lowest-common-denominator of syslog, but we could be preserving
> > fields.
> >  * Documentation and examples for the native journald APIs
> >  * Documented deployment strategies for recording append-only logs of
> > the hash chains
> >  * Other suggestions?
> 
> I'm somewhat concerned about the large amount of CPU utilization
> that I've seen with the journal, so, I'd consider putting some time
> into optimizing the journal internal code.
> 
> The concern was that on one of our systems we had a large amount
> of output being piped through journald. And with a ~12 second boot,
> the total CPU consumption of the journal alone was 2+ seconds.

Hmm, there shouldn't be too much CPU intensive stuff we do
actually... Maybe this is the XZ stuff (again)? But usually that would
only be used for really big log data....

Lennart

-- 
Lennart Poettering - Red Hat, Inc.