PDP - Optimise Curio UI for PDP SP Operations

[TippyFlitsUK]

Checklist

• This is not a question or a support request. If you have any Curio related questions, please ask in the discussion forum.
• This is not a new feature request. If it is, please file a feature request instead.
• I have searched on the issue tracker and the discussion forum, and there is no existing related issue or discussion.
• I am running the Latest release, or the most recent RC(release candidate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.

Curio component

• PoRep Pipeline
• Snap Deals
• Market
• IPNI provider
• Curio UI
• Other

Improvement Suggestion

The current Curio web GUI is primarily designed with PoRep-based Storage Providers in mind. For example, the sidebar includes links to pages like Sectors, PoRep, Snap Deals, and other features that are specific to traditional sealing workflows. However, these options don’t apply to PDP-only Storage Providers and can create confusion or clutter in the user experience.

We’d like to propose an option that tailors the UI for PDP-only SPs - filtering the available menu items so that only PDP-relevant pages are shown. This would help streamline navigation and create a more intuitive experience for users operating solely within the PDP model.

Open to other ideas as well if there’s a better way to approach this!

[LesnyRumcajs]

It might make sense to include this in this issue; on a 32 GiB RAM VPS I get flooded with those logs:

2025-04-14T17:35:27.904Z        DEBUG   harmonytask     harmonytask/harmonytask.go:371  skipped scheduling UnsealDecode type tasks on due to Did not accept UnsealDecode task: out of RAM: required 57982058496 available 31171588096)
2025-04-14T17:35:30.948Z        DEBUG   harmonytask     harmonytask/harmonytask.go:371  skipped scheduling UnsealDecode type tasks on due to Did not accept UnsealDecode task: out of RAM: required 57982058496 available 31171588096)
2025-04-14T17:35:33.986Z        DEBUG   harmonytask     harmonytask/harmonytask.go:371  skipped scheduling UnsealDecode type tasks on due to Did not accept UnsealDecode task: out of RAM: required 57982058496 available 31171588096)
2025-04-14T17:35:37.024Z        DEBUG   harmonytask     harmonytask/harmonytask.go:371  skipped scheduling UnsealDecode type tasks on due to Did not accept UnsealDecode task: out of RAM: required 57982058496 available 31171588096)
2025-04-14T17:35:40.074Z        DEBUG   harmonytask     harmonytask/harmonytask.go:371  skipped scheduling UnsealDecode type tasks on due to Did not accept UnsealDecode task: out of RAM: required 57982058496 available 31171588096)
2025-04-14T17:35:43.124Z        DEBUG   harmonytask     harmonytask/harmonytask.go:371  skipped scheduling UnsealDecode type tasks on due to Did not accept UnsealDecode task: out of RAM: required 57982058496 available 31171588096)
2025-04-14T17:35:46.164Z        DEBUG   harmonytask     harmonytask/harmonytask.go:371  skipped scheduling UnsealDecode type tasks on due to Did not accept UnsealDecode task: out of RAM: required 57982058496 available 31171588096)
2025-04-14T17:35:49.205Z        DEBUG   harmonytask     harmonytask/harmonytask.go:371  skipped scheduling UnsealDecode type tasks on due to Did not accept UnsealDecode task: out of RAM: required 57982058496 available 31171588096)
2025-04-14T17:35:52.255Z        DEBUG   harmonytask     harmonytask/harmonytask.go:371  skipped scheduling UnsealDecode type tasks on due to Did not accept UnsealDecode task: out of RAM: required 57982058496 available 31171588096)
2025-04-14T17:35:55.299Z        DEBUG   harmonytask     harmonytask/harmonytask.go:371  skipped scheduling UnsealDecode type tasks on due to Did not accept UnsealDecode task: out of RAM: required 57982058496 available 31171588096)

This might be an issue for a regular SP operation, but 32 GiB should be plenty for PDP. It probably makes sense to filter those out in such a case (and if it's an issue otherwise - probably it shouldn't be DEBUG but something more serious?).