RHEL6 & ext3 - Extreme delays (15-30secs) using msync(), flushing to an ext3 filesystem

Solution Verified - Updated -

Issue

  • An application utilizing a memory mapped file may well need to perform msync() on a frequent basis in order to maintain a hard copy of the in-memory database. There is potential for a noticeable performance degradation initiating the synchronization to an ext3 Filesystem on rhel6.

Environment

  • This problem is specific to utilizing the ext3 Filesystem on RHEL6 (2.6.32).
  • It was specifically reported in 2.6.32-358.18.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.