---
title: "Discussion on \"Parsed Results on Disk, Indexes in Memory\" | Hashnode"
description: "Discussion on \"Parsed Results on Disk, Indexes in Memory\". A book that has been opened once should not have to be parsed again on the second open. Parsing turns a file into chapters, paragraphs, and a cover image, and that work is slow enough that repeating i"
url: "https://hashnode.com/posts/parsed-results-on-disk-indexes-in-memory/6aeed6ec57a79bd868176043"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Parsed Results on Disk, Indexes in Memory](https://jbook.hashnode.dev/parsed-results-on-disk-indexes-in-memory?utm_source=hashnode&utm_medium=feed)

A book that has been opened once should not have to be parsed again on the second open. Parsing turns a file into chapters, paragraphs, and a cover image, and that work is slow enough that repeating i

5d ago · 5 min read · jbook.hashnode.dev  
Read the article

-   [#caching](https://hashnode.com/tag/caching)
-   [#storage](https://hashnode.com/tag/storage)
-   [#indexing](https://hashnode.com/tag/indexing)

## Written by

[jbook](https://hashnode.com/@jbook)

@jbook

  
[View profile](https://hashnode.com/@jbook)

Writing about ebook technology.

Writing about ebook technology.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.