Since upgrading from 4.12.4 to 5.0.2, we observe huge memory usage for XRootD processes even after just a few hours of runtime. Sadly, not easily visible in our test setup, but only with a heavy rate of incoming requests as seen in production.

It seems to affect only the data transfer nodes, not the redirector. On the transfer nodes, I see RSS up to 27 GB after 4-6 hours of heavy transfers (thousands of connections). One less ugly example is:

VmPeak: 10657644 kB
VmSize: 10657644 kB
VmLck:         0 kB
VmPin:         0 kB
VmHWM:   8422532 kB
VmRSS:   8422532 kB
RssAnon:         8413632 kB
RssFile:            8900 kB
RssShmem:              0 kB
VmData: 10496300 kB
VmStk:       132 kB
VmExe:        76 kB
VmLib:     18944 kB
VmPTE:     17140 kB
VmSwap:    18024 kB

I first wanted to ask if there's a "recommended debugging" way for these matters — of course I know my way around valgrind and gdb, but attaching these to a production xrootd instance is not really a possibility. I will try to reproduce this in our test setup when a sufficient time slot pops up, but if there is a "best practice" or something like a dump function to dump current allocated memory segments and their use in XRootD please let me know.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1291", "url": "https://github.com/xrootd/xrootd/issues/1291", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1