[FEATURE] Add in documentation minimal or preferred requirements

[edegraaff]

Is your feature request related to a problem?

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the Solution You'd Like

If you want to run open hamclock smoothly what type model of raspberry pi or others would be the best and or minimal choice. I run it on a pi3b+ and it works but.. way to slow.
A clear and concise description of what you want to happen.

Describe Alternatives You've Considered

Use the web based solution but this demands internet

A clear and concise description of any alternative solutions or features you've considered.
alternative hardware

Use Case

How would this feature benefit amateur radio operators? Be specific about the use case:

• [X ] General HF operation
• [ X] VHF/UHF operation
• [ X] Satellite operation
• Contesting
• [ X] POTA/SOTA
• [ X] DXing
• [ X] Emergency communications
• Other: **___**

Would you be willing to help implement this?

• Yes, I can submit a PR
• [ X] Yes, I can help test
• No, but I'd use it!

Additional Context

Add any other context, screenshots, or mockups about the feature request here.

Similar Features in Other Software

Are there similar features in other amateur radio software? If so, what do you like/dislike about their implementation?
Regards PD1EG

73!

[accius]

Added in 0eb071f, ships with v26.6.0: the README Deployment section now opens with a Hardware Requirements table. Short version for your case: a Pi 3B+ is our stated minimum and your experience is exactly why — it works, but map rendering is the heavy part and that hardware struggles with several layers on. Recommended for a smooth kiosk display is a Pi 4 (2GB+) or Pi 5. On the 3B+ specifically: enable Low Memory Mode in Settings, keep the layer count modest, and prefer the Flat projection — or run the 3B+ as server-only and point a faster machine's browser at it, which it handles fine.

73, K0CJH