You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SemanticDB is pretty interesting because it allows to develop tools that weren't possible before at scale that wasn't possible before. For more than a year, this allowed us not to care about its performance at all.
However, now the time has come to study and optimize SemanticDB. Let's start with benchmarking, just with the read-only aspect (since that's the only aspect that's relevant for M2, read-write will be part of M3).
The text was updated successfully, but these errors were encountered:
SemanticDB is pretty interesting because it allows to develop tools that weren't possible before at scale that wasn't possible before. For more than a year, this allowed us not to care about its performance at all.
However, now the time has come to study and optimize SemanticDB. Let's start with benchmarking, just with the read-only aspect (since that's the only aspect that's relevant for M2, read-write will be part of M3).
The text was updated successfully, but these errors were encountered: