Have something to say?

Tell us how we could make the product more useful to you.

In Progress

Geo-distributed Monitoring Instances (Internal Feature Proposal)

Enable the ability to run multiple instances of the Monitoring service in different data centers around the world. Each instance performs HTTP/PING/MTR checks from its geo-location and reports latency, number of hops, and full MTR output. This enables us to show users how their server performs from various locations. This would be a paid add-on to the base monitoring service. Instance Identification: Each instance assigned a unique location_id,… Monitoring Result Extensions: Extend result schema with: location_id, latency_ms, hop_count, mtr_output,… API Enhancements: API by specific location and plan Workload Distribution: Each instance only runs assigned checks (region-specific or filtered by tags) Business Add-on Strategy: Free Plan/ Paid Add-on

Antonio Ford 6 months ago

💡 Feature Request

In Progress

Reintroduce High-Frequency CPUs

First, I must say I love Webdock, the additional tooling that is provided, the clear API, and also the transparency related to issues appearing and the speed at which issues are solved. Now, unfortunately, I heard the Ryzen product line is discontinued. I think the Ryzen offering made Webdock very competitive. High-frequency CPUs and a sustainable hosting provider are a great combination. Either having slow Xeons for an incredible price or having incredibly fast Ryzen for also an incredible price/value made Webdock stand out. The new Epyc offering is somewhat in between those two but with pricing very similar to the former Ryzen plans (about 7% cheaper). In my initial benchmarking, the Epyc servers unfortunately perform 30-50% slower than the Ryzen counterparts for WordPress/SQL workloads. The performance is also very close to Hetzner’s AMD offering now, which is offered for a much lower price and generally has better uptime in my experience. I hope Webdock will reintroduce high-frequency CPUs, such as the high-frequency Epyc counterparts of Ryzen or other Ryzen CPUs (e.g. the 7900 or 9900 provide a lot of speed against relatively advantageous power usage, compared to top-of-the-line 7950x/9950x). There are other sustainable providers out there who offer Ryzen hosting at similar price levels, but they are unfortunately not as catered to developers as Webdock. So I really would like Webdock to offer high-frequency plans again. Addendum: some benchmark data, benchmarked on Xeon 2c/4GB, Epyc 2c/4gb and Ryzen 2c/4gb, using the default WordPress installation WordPress Post Query Test Inserting, Querying, Deleting 10000 posts Ryzen: 20.9 seconds Epyc: 30.7 seconds Xeon: 116,7 seconds WordPress Benchmark Plugin - Test PHP, SQL, Disk and Network Performance Ryzen: 9.4 overall score (PHP, SQL, File & Network tests are all significantly faster) Epyc: 7.6 score Xeon: 7.4 score (SQL and PHP are slower than Epyc here, the rest is similar) WordPress Performance Tester - WordPress Benchmark Plugin Ryzen: 6.003 score (lower is better) Epyc: 9.278 score Xeon: 10.399 score h2load load tester - requests per second the server can handle Ryzen: 83.79 requests / second Epyc: 65.55 requests / second Xeon: 35.27 requests / second

Michiel About 1 year ago

5

💡 Feature Request

Planned

Allow custom Icons and "What is installed here" strings

On the servers metadata we can choose “what is installed here”, which allows for a limited set of services with icons. I would like to: A) be able to add my own icon (perhaps a png or ico file or whatever you would deem adequate, could even be a more well packed library of icons) B) Provide my own “string”, that is, the name of “what is installed here” For example - there is no “WireGuard”, which is a pretty common service. Or “MailCow”. Or “else”. Like… what if my own CMS is installed there? Or a AspirePress Cloud instance? It would be really awesome (but of course no showstopper if not) to have more control over what is shown and addable there. Thanks!

Beda Schmid Over 1 year ago

3

💡 Feature Request

Suggestions to improve Account Validation Experience

I'd have an improvement suggestion to make this process less fragile: - let the user log in even if their email address hasn't been verified yet (this would also solve the pw right/wrong indication issue) - when a new user creates a new account, keep it in a 'limited' state (before asking for credit card data for example...) to make it obvious that the email has not been verified yet. - right beside the email address please provide a "Resend verification email" button which the user could press without support staff intervention - in case existing users changing their email address, keep the original one fully active as long as the new one has not been not verified successfully.

Philip C Over 1 year ago

💡 Feature Request