1 / 6

Old Client Memory Issues

Old Client Memory Issues. ATLAS FAX Meeting September 23, 2013 Andrew Hanushevsky, SLAC http://xrootd.org. What The XRootD Client Does. Allocates a memory cache for each open file By this is zero but the proxy server default is 512MB This is historical but unfortunately still true

neva
Download Presentation

Old Client Memory Issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Old Client Memory Issues ATLAS FAX Meeting September 23, 2013 Andrew Hanushevsky, SLAC http://xrootd.org

  2. What The XRootDClient Does • Allocates a memory cache for each open file • By this is zero but the proxy server default is 512MB • This is historical but unfortunately still true • Uses a lazy thread model • Each open file may wind up using a thread • Normally true for heavy reading and writing • Idle threads are reclaimed in the background • A scan is made every 30 seconds • And competes with other activities

  3. What Are The Effects? • Largely immaterial for normal analysis jobs • These are not very heavy uses of the client • Such jobs use TTree-Cache not the client cache • Can provoke high memory usage in concentrated uses • Typically, the proxy server that uses the client • Active proxy servers can see high memory usage • The default cache allocation policy • Slow thread stack de-allocation • Above exacerbated by SL6 memory allocation • Several bugs in glibcmalloc routines • Presumably last one fixed 3/14/13

  4. What Are The Mitigations? • This largely applies only to the proxy server • Add the following to the config file • pss.setoptReadCacheSize0 • Set the following envarbefore starting the proxy • MALLOC_ARENA_MAX=1 • Normally exported in /etc/sysconfig/xrootd • Be very careful to apply it only to the proxy!

  5. Will That Really Work? • Apparently not in RH 6.2 glibc-2.12-1.47.el6.x86_64 • See https://bugzilla.redhat.com/show_bug.cgi?id=799327 • So, try also setting MALLOC_CHECK_=1 • Unfortunately, this will use a lot more CPU • You can read the gruesome details at • https://www.ibm.com/developerworks/community/blogs/kevgrig/entry/linux_glibc_2_10_rhel_6_malloc_may_show_excessive_virtual_memory_usage?lang=en

  6. What About XRootD Itself? • If you see bloat we recommend • MALLOC_ARENA_MAX=4 • Normally exported in /etc/sysconfig/xrootd • We have seen this issue at SLAC and elsewhere

More Related