 | syslog-ng | 182 Members |
| 3 Servers |
| syslog-ng | 182 Members |
| 3 Servers |
| Sender | Message | Time |
|---|---|---|
| 26 Jul 2023 | ||
 czp | Norm1 and norm2 are without parallelize(), para1 and para2 are with parallelize() | 10:39:15 |
| czp | For the single client scenario there is roughtly a 40% performance increase. | 10:41:20 |
| czp | * For the single client scenario there is roughly a 40% performance increase. | 10:41:32 |
| czp | When there are many clients, then there is a minimal performance decrease, most visible around 50 clients. | 10:43:24 |
| czp |  Download sng43norm_vs_parallelize_vs_old.png | 10:46:24 |
| czp | And here comes the "everything was better in the good old times" graph: same hardware, but older openSUSE and syslog-ng versions 🙂 | 10:46:24 |
| czp | The parallelize tests were done on openSUSE Leap 15.5 and syslog-ng 4.3.0. | 10:47:28 |
| czp | The old measurement was done on the same AMD 5800X box, but openSUSE Leap 15.2 and syslog-ng 3.26. | 10:48:11 |
| czp | And a quick test with syslog-ng 4.0 (the oldest syslog-ng version I could find for openSUSE 15.5): | 11:17:44 |
| czp |  Download image.png | 11:17:47 |
| czp | Using the distro (complex) config and many connections, it's much faster than syslog-ng 4.3 on the same OS and hardware. | 11:19:33 |
 kefiras_32705 joined the room. | 18:18:59 | |
| 27 Jul 2023 | ||
 grg_2145 | Hi, I opened the issue https://github.com/syslog-ng/syslog-ng/issues/4566 about using the same python parser multiple times, causes syslog-ng to segfault on shutdown, I don't know what is the difference between mine and the one which Bazsi gave in https://github.com/syslog-ng/syslog-ng/pull/4552 but the latter does not segfaults. I encountered it whem I was trying to add testcases for the original pr, into testdb so that we will have this tested, unfortenately the tcs are failing because of this. (not pushed yet) | 07:50:17 |
| grg_2145 | * Hi, I opened the issue https://github.com/syslog-ng/syslog-ng/issues/4566 about using the same python parser multiple times, causes syslog-ng to segfault on shutdown, I don't know what is the difference between mine and the one which Bazsi gave in https://github.com/syslog-ng/syslog-ng/pull/4552 but the latter does not segfaults. I encountered it whem I was trying to add testcases for the original pr, into testdb so that we will have this tested, unfortenately the tcs are failing because of this. (not pushed yet) Edit I just checked it it happening on reload as well | 07:55:53 |
| czp | Having ivykis "officially" updated with your PR instead of patching it would be fantastic. | 10:54:51 |
| czp | I just ran into a problem on FreeBSD: if ivykis is installed on the system, compiling of syslog-ng fails, even if using --with-ivykis=internal | 10:56:14 |
| czp | Until now I compiled syslog-ng with internal ivykis, but for 4.3.0 I have to change ports to use ivykis from system, otherwise compilation might fail. | 10:57:32 |
 gokhanadev joined the room. | 13:47:04 | |
| 28 Jul 2023 | ||
 hofione | Same on macOS, I created a bug for this and hopefully will be able to work on it next week | 18:41:29 |
 bazsi77 | Can you post an error log? | 19:14:06 |
| czp | This is from FreeBSD, when Cy tried to compile syslog-ng with internal ivykis, while ivykis was also installed on the system: | 19:16:15 |
| czp | libtool: link: cc -Wshadow -Wno-stack-protector -Wno-unused-parameter -Wno-variadic-macros -O2 -g -Wno-initializer-overrides -O2 -pipe -pipe -fstack-protector-strong -fno-strict-aliasing -fstack-protector-strong -o modules/correlation/pdbtool/.libs/pdbtool modules/correlation/pdbtool/pdbtool-pdbtool.o -Wl,--export-dynamic ./lib/.libs/libsyslog-ng.so ./modules/correlation/.libs/libsyslog-ng-patterndb.a /export/wrkdir/amd64/export/freebsd/git/ports/sysutils/syslog-ng/work/syslog-ng-4.3.0/lib/.libs/libsyslog-ng.so -L/usr/local/lib /export/wrkdir/amd64/export/freebsd/git/ports/sysutils/syslog-ng/work/syslog-ng-4.3.0/lib/eventlog/src/.libs/libevtlog.so -L./lib/ivykis/src -livykis /export/wrkdir/amd64/export/freebsd/git/ports/sysutils/syslog-ng/work/syslog-ng-4.3.0/lib/secret-storage/.libs/libsecret-storage.so -L/usr/lib -lcrypto -lssl -lm -lrt -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lintl ./lib/eventlog/src/.libs/libevtlog.so ./lib/secret-storage/.libs/libsecret-storage.so -lpcre2-8 -lregex -ldl -pthread -Wl,-rpath -Wl,/usr/local/lib ld: error: undefined reference due to --no-allow-shlib-undefined: iv_work_pool_submit_continuation referenced by ./lib/.libs/libsyslog-ng.so | 19:16:18 |
| bazsi77 | It seems it is linking against the system ivykis | 19:16:22 |
| bazsi77 | While we detected the required functionality in the bundled one. | 19:16:41 |
| bazsi77 | It seems that the -L option for /use/local/lib comes first | 19:17:58 |
| bazsi77 | If you move -L/usr/local/lib to somewhat later in the command line, does that help? | 19:19:08 |
| bazsi77 | The issue is that the -L option for /usr/local/lib might be coming from another dependency, I am not sure what adds it | 19:19:41 |
| bazsi77 | I know. I was just saying it might be difficult to get that -L to be later, when generated by configure. But I will check. | 19:24:51 |
| 29 Jul 2023 | ||
 harmonious_guava_50390 joined the room. | 08:29:44 | |
| 1 Aug 2023 | ||
 taotaowang_74689 joined the room. | 02:13:48 | |