[syslog-ng] 3.4 - degraded single threaded performance
Evan Rempel
erempel at uvic.ca
Tue Jan 22 00:09:46 CET 2013
Sorry, this is more readable..
2.47% syslog-ng ld-2.12.so [.] _dl_update_slotinfo ▒
2.20% syslog-ng [kernel.kallsyms] [k] _spin_unlock_irqrestore ▒
1.92% syslog-ng libcrypto.so.1.0.0 [.] lh_insert ▒
1.65% syslog-ng libsyslog-ng-3.4.0rc2.so [.] log_multiplexer_queue ▒
1.65% syslog-ng libsyslog-ng-3.4.0rc2.so [.] nv_table_add_value ▒
1.65% syslog-ng ld-2.12.so [.] strcmp ▒
1.37% syslog-ng libsyslog-ng-3.4.0rc2.so [.] find_eom ▒
1.37% syslog-ng libc-2.12.so [.] _int_malloc ▒
1.10% syslog-ng libglib-2.0.so.0.2200.5 [.] g_atomic_int_add ▒
1.10% syslog-ng libc-2.12.so [.] vfprintf ▒
1.10% syslog-ng libc-2.12.so [.] memcpy ▒
1.10% syslog-ng ld-2.12.so [.] _dl_setup_hash ▒
1.10% syslog-ng ld-2.12.so [.] check_match.12442 ▒
1.10% syslog-ng ld-2.12.so [.] _dl_lookup_symbol_x ▒
1.10% syslog-ng ld-2.12.so [.] _dl_name_match_p ▒
1.10% syslog-ng [kernel.kallsyms] [k] __make_request ▒
0.82% syslog-ng libsyslog-ng-3.4.0rc2.so [.] log_msg_set_value ▒
0.82% syslog-ng libsyslog-ng-3.4.0rc2.so [.] log_reader_work_perform ▒
0.82% syslog-ng libsyslog-ng-3.4.0rc2.so [.] log_tags_inc_counter ▒
0.82% syslog-ng ld-2.12.so [.] _dl_relocate_object ▒
0.82% syslog-ng ld-2.12.so [.] __tls_get_addr ▒
0.82% syslog-ng [kernel.kallsyms] [k] native_flush_tlb ▒
0.82% syslog-ng [kernel.kallsyms] [k] error_exit ▒
0.55% syslog-ng libsyslog-ng-3.4.0rc2.so [.] log_msg_ack ▒
0.55% syslog-ng libsyslog-ng-3.4.0rc2.so [.] log_queue_fifo_push_tail ▒
0.55% syslog-ng libsyslog-ng-3.4.0rc2.so [.] nv_table_reserve_table_entry ▒
0.55% syslog-ng libsyslog-ng-3.4.0rc2.so [.] iv_inited ▒
0.55% syslog-ng libpthread-2.12.so [.] pthread_mutex_unlock ▒
0.55% syslog-ng libglib-2.0.so.0.2200.5 [.] g_static_private_get ▒
0.55% syslog-ng libc-2.12.so [.] _int_free ▒
0.55% syslog-ng libc-2.12.so [.] __strchrnul ▒
0.55% syslog-ng libc-2.12.so [.] __vsnprintf_chk ▒
0.55% syslog-ng libaffile.so [.] affile_dw_queue ▒
0.55% syslog-ng [kernel.kallsyms] [k] native_set_pmd ▒
0.55% syslog-ng [kernel.kallsyms] [k] __do_fault ▒
0.55% syslog-ng [kernel.kallsyms] [k] mmap_region ▒
0.55% syslog-ng [kernel.kallsyms] [k] kmem_cache_alloc ▒
0.55% syslog-ng [kernel.kallsyms] [k] path_put ▒
0.55% syslog-ng [kernel.kallsyms] [k] block_sync_page ▒
0.55% syslog-ng [kernel.kallsyms] [k] get_request ▒
0.55% syslog-ng [kernel.kallsyms] [k] __wait_on_bit ▒
On 01/21/2013 02:49 PM, Balazs Scheidler wrote:
> ----- Original message -----
> > Evan Rempel <erempel at uvic.ca <mailto:erempel at uvic.ca>> writes:
> >
> > > I took one of my syslog-ng 3.3 configuraiton files, which happens to
> > > read from a named pipe (/var/local/somename) and ran version 3.4rc2
> > > against it.
> > >
> > > I was only able toread bout 2,000 messages/sec through the pipe.
> > > With threaded(yes) I could read 100,000+/sec.
> > > With syslog-ng 3.3 I could read 100,000+/sec
> > >
> > > Is this the expected behaviour of threaded(no) with syslog-ng 3.4
> >
> > Nope, it definitely is not.
> >
>
> sounds like a bug to me too. I wonder how a perf output would look like.
>
> Does it saturate the cpu at 100% while this happens?
>
>
>
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>
--
Evan Rempel erempel at uvic.ca
Senior Systems Administrator 250.721.7691
Data Centre Services, University Systems, University of Victoria
More information about the syslog-ng
mailing list