I'm seeing around 6.37s here personally (while Hugo is building dtorg in around 388ms). (Sorry, didn't want to chase down dependencies to get the pelican version of darktable running - would have been a better comparison).
Guess a new machine makes a nice difference too. :) On Tue, Oct 12, 2021 at 10:46 AM Shlomi Fish <shlo...@shlomifish.org> wrote: > On Tue, 12 Oct 2021 18:18:52 +0300 > Shlomi Fish <shlo...@shlomifish.org> wrote: > > > Hi Pat, > > > > On Tue, 12 Oct 2021 09:52:25 -0500 > > Pat David via gimp-web-list <gimp-web-list@gnome.org> wrote: > > > > > Hello Shlomi and Marco! > > > > > > > 1. How is Hugo superior to Pelican wrt the gimp.org site? > > > > > > There are a few ways (this is based roughly on a fun dive through > various > > > static site generators over the last 6-7 years): > > > > > > 1. It's a self-contained binary for the generator. No other > requirements or > > > dependencies. > > > 2. It's under very active development by the community and pushes > updates > > > and security fixes almost every month (or a couple of times a month). > > > 3. It's FAST to build a site. Right now if you change something in > gimp.org > > > with Pelican it takes around 3-4 minutes to build the site. Hugo has > been > > > building in a few seconds (for some of the other sites I've done that > are > > > not too far off in similar size). > > > > Even if you change the inner content of a single page? I think using > Pelican > > to build gimp.org (from scratch) was faster than 3 minutes here - I can > check > > again. > > > > Checked now: 17s for a first build; 12s for a rebuild: > > ``` > Done: Processed 144 articles, 1 draft, 0 hidden articles, 111 pages, 38 > hidden pages and 0 draft pages in 17.25 seconds. > pelican -s pelicanconf.py 12.64s user 0.49s system 73% cpu 17.909 total > (py3-venv) [shlomif@telaviv1 gimp-web]$ time pelican -s pelicanconf.py >& > ~/rebuild.txt > pelican -s pelicanconf.py >&~/rebuild.txt 12.35s user 0.47s system 99% cpu > 12.902 total > (py3-venv) [shlomif@telaviv1 gimp-web]$ gvim ~/y2 > (py3-venv) [shlomif@telaviv1 gimp-web]$ inxi > CPU: Dual Core Intel Core i3-2100 (-MT MCP-) > speed/min/max: 1596/1600/3100 MHz Kernel: 5.14.9-200.fc34.x86_64 x86_64 > Up: 2d 9h 5m Mem: 3137.4/7847.9 MiB (40.0%) > Storage: 1.82 TiB (36.1% used) Procs: 232 Shell: Zsh inxi: 3.3.06 > (py3-venv) [shlomif@telaviv1 gimp-web]$ inxi -CSG > System: > Host: telaviv1.shlomifish.org Kernel: 5.14.9-200.fc34.x86_64 x86_64 > bits: 64 Desktop: Xfce 4.16.0 Distro: Fedora release 34 (Thirty Four) > CPU: > Info: Dual Core model: Intel Core i3-2100 bits: 64 type: MT MCP cache: > L2: 3 MiB > Speed: 1596 MHz min/max: 1600/3100 MHz Core speeds (MHz): 1: 1596 > 2: 1627 3: 1625 4: 1596 > Graphics: > Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics > driver: i915 v: kernel > Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting > unloaded: fbdev,vesa resolution: 1920x1080~60Hz > OpenGL: renderer: Mesa DRI Intel HD Graphics 2000 (SNB GT1) > v: 3.3 Mesa 21.1.8 > (py3-venv) [shlomif@telaviv1 gimp-web]$ > > ``` > > > > 4. The source/output file organization is a better mental model of how > a > > > site would normally be built (pages for directories, lists, etc etc - > I had > > > to hack at Pelican to get the generator to build output similar to > what was > > > sitting on disk.). > > > 5. Easy i18n support out of the box (this might require some > modifications > > > to interface with po files to support marco, I'll look into it). > > > 6. Did I mention it's fast? > > > 7. We (pixls.us folks) have migrated all of the sites we're managing > over > > > to Hugo already (just finished up the darktable.org migration) so it > makes > > > it easier for me to ask other users to help out as they're already > familar > > > with the tooling (asking them to look at pelican usually results in > silence > > > in IRC... :D :D :D ). > > > > > > I have not gotten a consensus per se, other than to see if current > people > > > hacking at it would be ok with it (nmat, maybe Jehan but I haven't > bothered > > > him with this yet). > > > > > > Ultimately my hope would be that we can lower the barrier to entry for > > > creating content/posts on the site and possibly engage the broader > > > community more (one can hope...). > > > > > > > All these sound like good reasons. > > > > -- > > Shlomi Fish https://www.shlomifish.org/ > Interview with Ben Collins-Sussman - https://shlom.in/sussman > > Oh! I wish you could see the look on his face! Actually, I would have also > liked to see the look on his face, but just then I woke up from the dream. > — https://www.shlomifish.org/humour/TheEnemy/ > > Please reply to list if it's a mailing list post - https://shlom.in/reply > . > _______________________________________________ > gimp-web-list mailing list > gimp-web-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gimp-web-list > -- https://patdavid.net GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC _______________________________________________ gimp-web-list mailing list gimp-web-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-web-list
