Visit Our UNIX and Linux User Community

Top Forums Web Development Some Typical Discourse Docker (Standalone) Rebuild, Restore and Update Times Post 303045708 by Neo on Friday 10th of April 2020 12:40:31 AM
Old 04-10-2020
Some Typical Discourse Docker (Standalone) Rebuild, Restore and Update Times

Just some notes on some typical tasks for Discourse and how long they take:

Restore Postgres DB (Linux Ubuntu, 8 Core 32 GB RAM)

Code:
# time ./restoreneo     // simple script that does a command line restore
cd /var/www/discourse
discourse enable_restore
Restore are now permitted. Disable them with `disable_restore`
begin neo restore
....
...
....

Marking restore as finished...
Notifying 'system' of the end of the restore...
Finished!
[SUCCESS]
Restore done.
discourse disable_restore
Restore are now forbidden. Enable them with `enable_restore`

real	9m58.273s
user	2m20.157s
sys	1m26.850s
root@community-app:/shared/neo/bin#

Rebuild Discourse Docker standalone app which is already installed (MacOS MacPro (Last 2013) 12-Core, 64GB RAM)

Code:
# ./launcher rebuild app

WARNING: We are about to start downloading the Discourse base image
This process may take anywhere between a few minutes to an hour, depending on your network speed

Please be patient

...
...
...

real	7m18.784s
user	0m1.694s
sys	0m1.116s
#

This User Gave Thanks to Neo For This Post:
 
Test Your Knowledge in Computers #26
Difficulty: Easy
IPv6 addresses are 256 bits in length.
True or False?

5 More Discussions You Might Find Interesting

1. AIX

Restore previous update w/o multibos

Hi All, How do I restore previous state if my current update failed w/o multibos? Is that possible? Thanks in advance for any idea. (3 Replies)
Discussion started by: itik
3 Replies

2. Shell Programming and Scripting

rebuild/update fuppes database if files are added/removed from directory

The title says it all. I have a upnp server running fuppes that is connected to my xbox360. In order to see the files on the xbox360 i have to manually update and rebuild the database anytime i add or remove files. I have tried cron jobs to do it every 20 min which works, but if I am streaming... (0 Replies)
Discussion started by: tr6699
0 Replies

3. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Two

OK. Like we all do, we learn a lot from tests, test migrations, and so forth. Today, I started from scratch on test migration 2, armed with a lot more knowledge, The main differences are as follows: Installed discourse plugin ruby-bbcode-to-md before starting the install Modified... (30 Replies)
Discussion started by: Neo
30 Replies

4. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Four

Test Build 4 on New Server, with changes identified in discourse test builds 2 and 3, primarily: Insuring ruby-bbcode-to-markdown is enabled. Removing line breaks from ICODE to markdown in migration script. Added vbpostid to posts in discourse to setup migrating vb "thanks" to discourse... (28 Replies)
Discussion started by: Neo
28 Replies

5. What is on Your Mind?

Update on vB3 Migration to Discourse - Issues and Status of BBCode Transformations

We "completed" the migration of this vB3 site to Discourse a number of days ago. However, deeper testing by @Scrutinizer and @MadeInGermany revealed that a lot of text was mangled in the migration. We traced these bugs to two issues: A minor bug in the Ruby vbulletin.rb migration script... (19 Replies)
Discussion started by: Neo
19 Replies
TIMES(2)						     Linux Programmer's Manual							  TIMES(2)

NAME
times - get process times SYNOPSIS
#include <sys/times.h> clock_t times(struct tms *buf); DESCRIPTION
The times() function stores the current process times in the struct tms that buf points to. The struct tms is as defined in <sys/times.h>: struct tms { clock_t tms_utime; /* user time */ clock_t tms_stime; /* system time */ clock_t tms_cutime; /* user time of children */ clock_t tms_cstime; /* system time of children */ }; The tms_utime field contains the CPU time spent executing instructions of the calling process. The tms_stime field contains the CPU time spent in the system while executing tasks on behalf of the calling process. The tms_cutime field contains the sum of the tms_utime and tms_cutime values for all waited-for terminated children. The tms_cstime field contains the sum of the tms_stime and tms_cstime values for all waited-for terminated children. Times for terminated children (and their descendants) is added in at the moment wait(2) or waitpid(2) returns their process ID. In particu- lar, times of grandchildren that the children did not wait for are never seen. All times reported are in clock ticks. RETURN VALUE
The function times returns the number of clock ticks that have elapsed since an arbitrary point in the past. For Linux this point is the moment the system was booted. This return value may overflow the possible range of type clock_t. On error, (clock_t) -1 is returned, and errno is set appropriately. NOTES
The number of clock ticks per second can be obtained using sysconf(_SC_CLK_TCK); In POSIX-1996 the symbol CLK_TCK (defined in <time.h>) is mentioned as obsolescent. It is obsolete now. On Linux, if the disposition of SIGCHLD is set to SIG_IGN then the times of terminated children are automatically included in the tms_cstime and tms_cutime fields, although POSIX 1003.1-2001 says that this should only happen if the calling process wait()s on its chil- dren. Note that clock(3) returns values of type clock_t that are not measured in clock ticks but in CLOCKS_PER_SEC. CONFORMING TO
SVr4, SVID, POSIX, X/OPEN, BSD 4.3 HISTORICAL NOTES
SVr1-3 returns long and the struct members are of type time_t although they store clock ticks, not seconds since the epoch. V7 used long for the struct members, because it had no type time_t yet. On older systems the number of clock ticks per second is given by the variable HZ. SEE ALSO
time(1), getrusage(2), wait(2), clock(3), sysconf(3) Linux 2002-06-14 TIMES(2)

Featured Tech Videos

All times are GMT -4. The time now is 01:37 PM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy