These are some thoughts I had when evaluating the project and the website which may be useful.
Eventually during the next upgrade to the site one might consider using Discourse instead of phpbb 3. Discourse modern platform, scales well to mobile devices, extensible with plug-ins, completely open source, easy to use with markdown support and in my opinion aesthetically pleasing.
Some of the performance ratings to some degree seem a bit arbitrary on the download page one http://dietpi.com/ where it displays supported hardware. I find it helpful although any statistics that we know of based on average performance should be included if available.
Include in the get started page a link to a guide to utilize dietpi.txt.
It would be helpful if the DietPi-Software that shows details for all installation options included the ‘Install ID/current index’ and a legend that displayed which platforms individual software are not available. This allows the user to create a dietpi.txt automated install without ever booting up a device to obtain IDs or rooting around in Github. It helps mitigate expectations of end-users of booting up their device and finding software “missing” because they didn’t realize it wasn’t supported by their device due to the limitations.
An Example that definitely could be more polished.
Gogs - GitHub style server, with web interface. #49 (N/A - Odroid C2)
Thanks for the feedbacks and suggestions to improving our website. When I get some free time, i’ll go through all your suggestions.
Some of the performance ratings to some degree seem a bit arbitrary on the download page one > http://dietpi.com/ > where it displays supported hardware.
Theres are just rough guides based on my knowledge and experience with the devices and their hardware capabilities. If people are willing to do indepth tests and upload their results for us to use, i’ll get them linked in and we can adjust scores as needed.
But generally speaking: CPU performance rating is based on:
CPU clock freq
CPU cores total
Network performance rating is based on:
1% = 10Mbit
For the case of XU4 with current 3.x kernel, we only get around 400Mbit transfer rates.
RPi is through USB bus, so slighly lower than 10%
Heat Efficiency Rating:
0% = unable to run at full load without thermal throttling kicking in, XU4 special lasts 3 seconds.
1-50% = Requires heatsink, or is incapable to run at full load for a long periods of time.
50%+ = Generally considered able to run at full clocks for long periods of time.
It would be helpful if the DietPi-Software that shows details for all installation options included the ‘Install ID/current index’ and a legend that displayed which platforms individual software are not available.
Yep I’d love to get this added to the website as a list, but, its time consuming and will require constant maintenance (eg: Plex dropped support for ARMv6 few weeks ago).
If we can get someone to maintain this, i’d be up for it. But I cant really dedicate the time to this at the moment.
But as you are aware, following provides a list for the moment:
I dont have the knowledge to scrape dietpi-software list and convert it into a DB output/webpage yet. But thats probably a better solution if we can get some assistance on this.
I think integration of services offered as a platform could be if could be a feature along with improved security. This might be more of a future statement than the current one. All in good time.
An example that shows integration and improved security would be Fail2Ban integrated into existing services that would be applicable such as
I think it would be prudent to come up with a standard performance methodology for testing. Dietpi already have bench-marking capabilities for file system, ram, CPU and I/O performance. All we need is something to benchmark network performance that simple and that can be run on the local network. Last but not least model the hardware that’s being tested. Then the logs could be uploaded to http://dietpi.com for display.
I can see the issue with manually maintaining supported software per platform along with the ID numbers. Although I can’t help but think this might be automated. Possibly scraping the information directly from GitHub dietpi? That would need some thought.