Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Backup done! Super compliments 2.x look to use less ram and cpu then 1.x, I received the first email for a backup done and last part of this say:
Scheduled Backups Directory in 46445.64 ms
so, please tell me: how many ms we need to do a second?
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | backup_migrate_664474.patch | 1.09 KB | gapple |
Comments
Comment #1
ronan commentedGlad it's working out. ms is Milliseconds. 1000 ms per second. Your backup took 46 seconds to complete.
http://en.wikipedia.org/wiki/Millisecond
Computer timing is usually done in milliseconds for accuracy. I suppose I could convert to seconds to make it more user friendly, but it's a fairly easy bit of mental math and 46.44564 seconds doesn't look a whole lot more friendly.
Comment #2
gappleOne method I've seen in use that I think is pretty user-friendly but still functional, is to round the value for display but use a tooltip to show the full value. This way you could write "backup took 46.4 seconds" on the page (or minutes if more appropriate), and if anyone wants more specific information they can hover over the value to get "backup took precisely 46445.64 ms" in the tooltip.
I've attached a quick patch to show what I mean. It could use some styling to indicate that the value is now hover worthy (eg., a dotted underline). I wasn't sure if using an
<abbr>tag, which usually has an underline by default, would be appropriate instead of a<span>with custom styling.Comment #3
ronan commentedWell better late than never. This is now the behavior in the 3.x branch