We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
@crawlee/core
According to crawlee.dev, snapshotter considers total memory overloaded above 70% (0.7). In the actual implementation however, it only considers memory overloaded above 90%.
const { eventLoopSnapshotIntervalSecs = 0.5, clientSnapshotIntervalSecs = 1, snapshotHistorySecs = 30, maxBlockedMillis = 50, maxUsedMemoryRatio = 0.9, maxClientErrors = 3, log = defaultLog, config = Configuration.getGlobalConfig(), client = config.getStorageClient(), } = options;
I think this has been causing me some fun and games when loading some particularly heavy webpages such as file downloads.
NA, documentation issue
3.11
20
No response
next
The text was updated successfully, but these errors were encountered:
bab3b71
No branches or pull requests
Which package is this bug report for? If unsure which one to select, leave blank
@crawlee/core
Issue description
According to crawlee.dev, snapshotter considers total memory overloaded above 70% (0.7). In the actual implementation however, it only considers memory overloaded above 90%.
I think this has been causing me some fun and games when loading some particularly heavy webpages such as file downloads.
Code sample
Package version
3.11
Node.js version
20
Operating system
No response
Apify platform
I have tested this on the
next
releaseNo response
Other context
No response
The text was updated successfully, but these errors were encountered: