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
This is a possible, nice to have followup of #22554
Currently, the log stream when running npm install as part of storybook init is written directly to the hard drive. Users would be thankful if this operation could be avoided to avoid multiple write operations to the hard drive in a short period of time.
Instead, should we consider writing into memory instead, until the file is finally written? This has several benefits:
Write operations to the hard drive are slow in comparison to the memory
There is no need to clear the temporary file if error logs are not written to the hard drive; just clear the memory.
Reading from the temporary file can be avoided completely because we don't need it anymore
Let's just write to the hard drive, when it is necessary (producing the final log file), otherwise, let's avoid it as far as possible.
This is a possible, nice to have followup of #22554
Currently, the log stream when running
npm install
as part ofstorybook init
is written directly to the hard drive. Users would be thankful if this operation could be avoided to avoid multiple write operations to the hard drive in a short period of time.Instead, should we consider writing into memory instead, until the file is finally written? This has several benefits:
Let's just write to the hard drive, when it is necessary (producing the final log file), otherwise, let's avoid it as far as possible.
Originally posted by @valentinpalkovic in #22554 (comment)
The text was updated successfully, but these errors were encountered: