![]() That doesn’t seem like it should be more than linear, but I presume that somehow the higher layers are creating big lists of file records and copying them repeatedly or something. I’ve mostly noticed the slowness with listing a directory. Stuck When Upgrading Directly From macOS Mojave to Big SurĪpple File System (APFS) Apple Mail Carbon Copy Cloner Core Data Mac macOS 13 Ventura Optimization Spotlight Yeah, it seems like the B-Tree part in the filesystem shouldn’t care that much for lookups.If you navigate to the hidden Library folder in your home folder, then to Mail > V10 > Data, you’ll see folders named by number, four layers deep, until you finally get to a Messages folder with actual files in it.Īpple should also employ this technique for Core Data external storage and Spotlight temporary files. longer than 10 minutes) that the task aborts with an errorįor a contrasting example, consider how Mail organizes a potentially astronomic list of files. In extreme cases like this, the delay to retrieve a file list can be so long (i.e. In other words, more than 10% of the files on the whole startup disk were in that “media” folder. Upon closer analysis, we determined that the “media” folder had 181,274 files in it. Last week, one of our users found the task as shown above. Gathering the enormous file list will also take progressively longer as the list gets larger. Adding a new file, for example, requires that the filesystem compare the new item name to the name of every other file in the folder to check for conflicts, so trivial tasks like that will take progressively longer as the file count increases. I figure I’ll have to restart Mail by Friday, when the new message count should be well into the 1000s.Any time a folder has more than a few thousand items in it, the filesystem is going to be a lot slower when working with that folder. Time Memory Private Memory “New Messages” count in Downloading message Watching more closely for a bit, I see that while the memory use trends steadily upward, it’s more of a sawtooth pattern.Īs for memory consumption, here is a brief log for the past 18 hours or so: I erred in saying “monotonically increasing”. TL DR - Real Private Memory increases along with total memory. Typically, though, I restart Mail prophylactically at about 750MB and all is good. ![]() Sometimes the entire machine is affected (requiring a reboot). What I’ve seen in the past is that when Mail’s memory use approaches 1GB, Mail becomes unstable in various ways. This becomes a maintenance consideration, and I travel quite a bit (often off the grid), making regular maintenance restarts tricky.ĭo you see any particular bad effects when it gets to 1 GB? Does the Real Private Memory (you may need to tell it to show that column) also increase like that? Frankly, I wouldn’t much care except for the apparent memory-leak issue. Mail and SpamSieve are operating as expected EXCEPT for the persistent “downloading messages” message.Īny additional thoughts / suggestions much appreciated. Re-started Mail (went fine) then re-added that account (went fine). The rebuild went fine after I deleted what turned out to be a problematic account (it’s “Spam” folder was apparently a mess, causing Mail to think that there were ~450,000 messages in there - there weren’t). No change to the “downloading messages” behavior. Okay, I sucked it up and re-built Mail’s databases from scratch. If the rebuild succeeds, you could then re-import them later. Another idea would be to export some of the mailboxes and then delete them from Mail, so that there’s less to rebuild.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |