Overall Performance
Marked’s overall rendering speed and performance can vary greatly based on your settings in preferences and the type of content you have in your document. There are several factors that can lead to slow rendering or long delays:
- Rendering a Markdown document containing a lot of HTML. This will always take longer to process.
- Using the MultiMarkdown processor with the fenced code option enabled can lead to performance issues if there are a lot of code blocks in your document. Marked handles converting these outside of the standard processor, and there’s a small performance price to pay for the extra processing. In general, though, the fenced code option is well-optimized and can handle a programming book’s worth of code. If you have trouble in this area, consider using a custom processor with fenced code support built in.
- Using many includes. Whether it’s code includes or an index merge file, picking up all the pieces takes Marked a second. The same is true of large Scrivener documents. There’s not a lot you can do to fix this one, Marked will just do its best to keep up with the way you choose to structure your document.
- Hard drive condition. If your hard drive is almost full, your Spotlight index is corrupt or your permissions haven’t been repaired in a while, Marked may have a harder time picking up the changes to the file it’s watching. Optimizing your drive by repairing permissions will often help, and rebuilding the Spoglight index is often a fix for Marked issues.