Bug #373: cfuse is degenerate with respect to ptmalloc - CephFS - Ceph

Actions

Copy link

Bug #373

closed

cfuse is degenerate with respect to ptmalloc

Added by Greg Farnum over 13 years ago. Updated over 7 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Greg Farnum

Category:

Target version:

% Done:

Source:

Tags:

Backport:

Regression:

Severity:

Reviewed:

Affected Versions:

ceph-qa-suite:

Component(FS):

Labels (FS):

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

While running the test suite on cfuse I saw real memory usage climb up to 2GB. That doesn't quite seem correct. Determine if it's a memory leak or a heap fragmentation issue and try to fix.

Actions

Copy link

Updated by Sage Weil over 13 years ago

Target version changed from v0.23 to v0.22

Actions

Copy link

Updated by Greg Farnum over 13 years ago

While running the qa suite on flab, it's now up to 1.4GB. Tests run so far:
snaptest-xattrwb
snaptest-1
snaptest-2
iozone

In progress: snaptest-dir-rename

If we're lucky it's just one of these doing it, and I can identify the single test and run it through valgrind or something.

Actions

Copy link

Updated by Greg Farnum over 13 years ago

Oh, I misread that. Also completed: untar_snap_rm. In progress: kernel_untar_build

Actions

Copy link

Updated by Greg Farnum over 13 years ago

Subject changed from Memory leak in cfuse to cfuse is degenerate with respect to ptmalloc

Well, I ran it through massif. And it looks like cfuse, as with the MDS and OSD, is just degenerate for ptmalloc. massif reported peak usage of ~400MB. I tried switching to cfuse and ran the iozone test and it ended at ~650MB virtual/545MB resident. In previous tests I've seen it top 1.6GB virtual memory.
I'll have to look into how we use the client to see if linking it with tcmalloc is a viable solution.

Actions

Copy link