Evaluate ways to reduce operational costs

[leovegoda]

Is your feature request related to a problem? Please describe.
PeeringDB hosting costs have been on an upward trend over the last year. We should investigate ways to reduce operational costs without sacrificing service quality.

Who is affected by the problem?
Higher costs could require additional sponsorship or reduce service quality if not addressed by lowering operational costs.

What is the impact?
Improved financial efficiency

Are there security concerns?
No

Are there privacy concerns?
No

Describe the solution you'd like
An analysis that can be evaluated by PeeringDB Stewards

Do you think this feature will require a formal design?
Yes

Describe alternatives you've considered
More sponsorship

Could this feature request need support from the Admin Committee?
No

What is the proposed priority?
High

Provide a rationale for any/all of the above
We ought to sustain or improve value to sponsors while retaining or improving service levels

[arnoldnipper]

+1

IMO that must a joint task of OPS and the developers

[grizz]

+1

Agreed

[martinhannigan]

+1

…

On Mon, Aug 22, 2022 at 11:30 AM Matt Griswold ***@***.***> wrote: Agreed, +1 — Reply to this email directly, view it on GitHub <#1225 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFA2YQRFFVB3MARCKEFIR63V2OMKHANCNFSM56SEQOXQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[mcmanuss8]

+1

[leovegoda]

In implementing this issue, we'll look at deploying directly onto the cloud infrastructure, instead of deploying to a VM that runs on that infrastructure. It is hoped that this will help with efficient service scaling.