📢 Help Needed: Calling all Users/ Adopters to Contribute to Sizing Guide
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- kubernetes, mongodb
- Domain
- databases, documentation, infrastructure
Research direction
Read install/SIZING.md and follow its contribution instructions. Gather deployment resource allocations, environment details, scaling experiences, and performance observations for Microcks, MongoDB, and Keycloak. Done means the real-world data is added to the sizing guide in a useful, accurate form.
Written by the indexing model from the issue text.
Description
Describe the bug
Description
We've created a Sizing Guide for Microcks on Kubernetes and need YOUR real-world deployment data to make it accurate and comprehensive!
The guide helps users properly size their Microcks deployments based on expected usage patterns and resource requirements.
What we need:
- Resource allocations (CPU/memory for Microcks, MongoDB, Keycloak)
- Performance observations under different loads
- Environment specifications and scaling experiences
The guide contains detailed instructions on how to contribute your deployment data. Help the community avoid resource issues and make better sizing decisions!
Attach any resources that can help us understand the issue.
No response
- Dominant language
- No language data
- Stars
- 11
- Forks
- 9
- Avg merge
- 17m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microcks/community
-
Clarify and Formalize Steering Committee Membership Application ProcessPossibly taken @yada claimed this 6 days ago. Opensteering
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
steering
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
steering
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
documentation good first issue help wanted
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
documentation good first issue help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
All issues in microcks/community
Similar issues
-
Lint rule GV016 order-by-randomPossibly taken @YinL-k claimed this today. Openenhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
laaielichter/Gulliver#20 ·
Maintainers usually reply within 1 day
-
database documentation from-review-extraction severity:nit
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
LearningCircuit/local-deep-research#8217 ·
Maintainers usually reply within 1 day
-
"Sync columns from source" fails on ClickHouse tables with ALIAS, MATERIALIZED or DEFAULT columnsPossibly taken @bmuraykhi claimed this today. Open#bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bazel bug odb
Difficulty 1/5 Under an hour Newbie friendliness 80/100
The-OpenROAD-Project/OpenROAD#12095 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ClickHouse/clickhouse-go#2093 ·
Maintainers usually reply within 1 day