Implement async parsers #1352
Implement async parsers #1352
Conversation
msujew
force-pushed
the
msujew/async-parser-impl
branch
from
3d40610 to
5beae71
Compare
There was a problem hiding this comment.
Great stuff @msujew.
I just have some minor questions & remarks.
Btw. Would it work the same way (in principle) in the browser with webworkers?
| async parse<T extends AstNode>(text: string, cancelToken: CancellationToken): Promise<ParseResult<T>> { | ||
| const worker = await this.acquireParserWorker(cancelToken); | ||
| const deferred = new Deferred<ParseResult<T>>(); | ||
| deferred.disposables.push(cancelToken.onCancellationRequested(() => { |
There was a problem hiding this comment.
This code is very dense. Could you please separate this and motivate the attachment of the Disposable returned by the listener registration to deferred?
deferred is supposed to have a finite lifetime, right?
And onCanceled-Listeners won't be called multiple times, right?
There was a problem hiding this comment.
I've refactored this a bit, but it still works the same way. This is basically a safeguard: If the cancellation is requested after parsing has finished, we don't want to kill the worker anymore. The cancellation has a way longer lifetime than the deferred promise here. So we have to remove the listener again once were finished with it.
packages/langium/test/parser/worker-thread-async-parser.test.ts
Outdated
Show resolved
Hide resolved
| ...result, | ||
| value: dehydrated | ||
| }); | ||
| }); |
There was a problem hiding this comment.
Can this considered a blue print for worker implementations?
Or should everybody built one on it's own? A remark on that including some dos and dont's would be nice, here.
There was a problem hiding this comment.
Yes, everyone should build their own.
Do's: Parse the text and send the dehydrated AST back
Dont's: Anything else.
|
One more thing: |
msujew
force-pushed
the
msujew/async-parser-impl
branch
2 times, most recently
from
b626ca3 to
9d8d6ad
Compare
msujew
force-pushed
the
msujew/async-parser-impl
branch
from
9d8d6ad to
194ec01
Compare
A follow up on #1306.
Implements the basics to create an async parser based on node worker threads. While in theory this should be faster than the sync parser implementation (due to parallelisation), it might be slower on startup due to the time it takes for all the workers to start up. Once the threads are all up and running, it is indeed faster. The break even point is fairly late though, roughly after parsing ~2 million LoC.
The main benefit of this change is that it allows parser cancellation by simply killing workers. The cancellation happens after a timeout, since it needs to take the time it takes to create a new worker into account. The default is 200ms, but can be arbitrarily changed by adopters.
Most of the change is actually just the new
Hydratorservice which tries to dehydrate/hydrate AST nodes to be processed by the structured cloning algorithm of workers.