No description
RQ now has experimental support for workerpools. When to use this? Roughly when you have more than 2 workers a workerpool might make sense, below 2 it's overhead as master "pool" process will need to run to manager workerpool itself. Why is it any better? Currently we just let supervisor duplicate the worker process N number of times. This is inefficient from shared memory POV. Forking the original process to create workers enables sharing of more memory thus leading upwards of 60-70% reduction in memory usage with pool size of 8 workers. |
||
|---|---|---|
| .github | ||
| cypress | ||
| esbuild | ||
| frappe | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .flake8 | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .mergify.yml | ||
| .pre-commit-config.yaml | ||
| .releaserc | ||
| .semgrepignore | ||
| attributions.md | ||
| CODE_OF_CONDUCT.md | ||
| codecov.yml | ||
| CODEOWNERS | ||
| commitlint.config.js | ||
| cypress.config.js | ||
| generate_bootstrap_theme.js | ||
| hooks.md | ||
| LICENSE | ||
| node_utils.js | ||
| package.json | ||
| pyproject.toml | ||
| README.md | ||
| SECURITY.md | ||
| sider.yml | ||
| socketio.js | ||
| yarn.lock | ||
Full-stack web application framework that uses Python and MariaDB on the server side and a tightly integrated client side library. Built for ERPNext.
Login for the PWD site: (username: Administrator, password: admin)
Table of Contents
Installation
Production
- Managed Hosting on Frappe Cloud
- Easy install script using Docker images
- Manual install using Docker images
Development
Contributing
Resources
- frappeframework.com - Official documentation of the Frappe Framework.
- frappe.school - Pick from the various courses by the maintainers or from the community.
License
This repository has been released under the MIT License.
By contributing to Frappe, you agree that your contributions will be licensed under its MIT License.