User Interfaces

The Logs and Queries tab is very crucial to finding queries that may be overused or are not performant, however there is no way to be able to copy the query and I often find myself screenshotting the tooltip and manually typing the query to do local testing. This is EXTREMELY cumbersome and adding a copy icon in the query column would be GREAT! There is already a dotted line when clicked which makes me think it was copied but in reality it does nothing.

Many cloud IDEs as well as online code schools have highly functional browser-based terminals. I believe many use Xterm.js. * Cloud9 * JupyterLab * Eclipse Che/Orioin * codeschoo.com * codeacademy.com * RStudio Server The current console has numerous problems. You cannot cut and paste. The pipe symbol does not work.

It is strange that the "Apps" section is not part of a team. Although it may seem like it isn't hard to find, if you are a new user, finding the apps section if you are apart of a team is annoying if it isn't in the team Project. Not just that, it is so much better to have everything in one place instead of needing to go around everywhere to find other items.

It would be great to have user have the ability to add the recovery ISO via the dashboard rather than contacting support and adding and removing them. With the option in dashboard it will more easy for the droplet owners to rectify errors and boot issues.

After asking support team how memory usage is calculated, their answer was: Our memory calculation is as follows: (MemTotal - MemFree - Cache) / MemTotal This values are taken from /proc/meminfo. If I do the math, I get the exact number as the graph is showing. But, I don’t think the calculation is accurate. See some information found: (Linux kernel source tree) Many load balancing and workload placing programs check /proc/meminfo to estimate how much free memory is available. They generally do this by adding up "free" and "cached", which was fine ten years ago, but is pretty much guaranteed to be wrong today. It is wrong because Cached includes memory that is not freeable as page cache, for example shared memory segments, tmpfs, and ramfs, and it does not include reclaimable slab memory, which can take up a large fraction of system memory on mostly idle systems with lots of files. Currently, the amount of memory that is available for a new workload, without pushing the system into swap, can be estimated from MemFree, Active(file), Inactive(file), and SReclaimable, as well as the "low" watermarks from /proc/zoneinfo. However, this may change in the future, and user space really should not be expected to know kernel internals to come up with an estimate for the amount of free memory. It is more convenient to provide such an estimate in /proc/meminfo. If things change in the future, we only have to change it in one place. This is where MemAvailable was born: An estimate of how much memory is available for starting new applications, without swapping. Calculated from MemFree, SReclaimable, the size of the file LRU lists, and the low watermarks in each zone. The estimate takes into account that the system needs some page cache to function well, and that not all reclaimable slab will be reclaimable, due to items being in use. The impact of those factors will vary from system to system. Wouldn't be better to calculate memory usage as: (MemTotal - MemAvailable) / MemTotal