Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve Performance #9

Open
pawandubey opened this issue Jun 20, 2015 · 0 comments
Open

Improve Performance #9

pawandubey opened this issue Jun 20, 2015 · 0 comments

Comments

@pawandubey
Copy link
Owner

Right now (as of today) Griffin can parse 1000 markdown documents containing the following text : Sample text in ~5 seconds.
According to simple benchmarking and profiling, 80% of the time is taken by the Parser.writeFile method.

Task: Seek ways to improve performance of this method, for faster writing. Probably by using limited byte buffers instead of writing line by line.
Objective: Improve performance. Desirably, ~1 second to parse 1000 files.
This was referenced Jun 20, 2015
Closed
Closed
pawandubey added a commit that referenced this issue Jun 25, 2015
@pawandubey
Improved Performace by refactoring template compilation out to happen…
11f04cd 
… only once. Solves #9
This was referenced Jun 30, 2015
Closed
Closed
pawandubey added a commit that referenced this issue Jul 4, 2015
@pawandubey
Disk Cache! Stupendous performance increase! Solves #9 and #34.
ff5fd49 
-Caching of all Data variables to the cache.db file.
-Now reads from the cache and does a quick parse by default.
pawandubey added a commit that referenced this issue Jul 4, 2015
@pawandubey
Big changes. Support caching, multithreaded writing of tags and a new…
8a4773c 
… CLI command!

-support for caching by default. Refer to previous commit. #34
-Tags are created by multiple threads with proper lock-resolution to avoid race conditions. #9 and #27
-Fixed issue with fast parsing. It now updates all relevant data structures with appropriate data. #33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pawandubey