Subject: KampalaMeetingLog-2018-03-15.txt Date: March 15, 2018 at 3:46:10 PM PDT ---++ #twiki_release on IRC [15:00:31]   hi HideyoImazu-san [15:00:37]   Hi Peter [15:00:56]   time of the year when the meeting starts early [15:01:00]   for you [15:01:12]   sorry about that [15:01:18]   no worries [15:01:43]   there are other US time based meetings too [15:02:11]   ah ---++ TWiki #release on Slack peterthoeny [3:01 PM] hi @haj & @himazu himazu [3:02 PM] hi @peterthoeny peterthoeny [3:03 PM] there is a short time when the time difference between europe and usa is out of sync this week it is himazu [3:03 PM] yep peterthoeny [3:03 PM] our meeting is now at 11pm instead of midnight in europe maybe @haj missed the change himazu [3:03 PM] I have this meeting in PT on my calendar peterthoeny [3:04 PM] i sent him an email, let’s see if he shows up what’s new besides twiki? himazu [3:04 PM] and other US time based meetings shift too. So I have little problem with this release meeting shifting time in Japan time zone I started having allergy symptom you may see my FB posting about that peterthoeny [3:06 PM] i am sorry about the allergy issues himazu [3:06 PM] And I got to know “Ich glaub mein Schwein pfeit” peterthoeny [3:07 PM] 花粉症? himazu [3:07 PM] yes peterthoeny [3:08 PM] pfeit? himazu [3:08 PM] confirmed by an allergy check peterthoeny [3:08 PM] ah, never heard that expression himazu [3:08 PM] pfeift peterthoeny [3:09 PM] yup himazu [3:09 PM] it heard it’s a common German idiom. peterthoeny [3:10 PM] we had an exceptional sunset yesterday: https://www.flickr.com/photos/peterthoeny/40776444672/in/photostream/lightbox/ FlickrPeterThoeny I'm flyin', I'm flyin' high like a bird https://farm5.staticflickr.com/4785/40776444672_a3eced3085_b.jpg himazu [3:10 PM] beautiful peterthoeny [3:10 PM] it only lasted for a minute like that himazu [3:10 PM] looks like a painting I would totally believe if you said it’s a painting peterthoeny [3:11 PM] well, it is paintery hdr (the center), the periphery is photographic haha, fast painting done in 30 min :slightly_smiling_face: that’s how long the post processing took himazu [3:12 PM] 30 min! peterthoeny [3:12 PM] that’s fast because i am getting used to it it used to take me 1h himazu [3:13 PM] maybe you are thinking about getting a PC with multiple GPUs? or 30 min is taken with that kind of PC? peterthoeny [3:14 PM] well, it’s more my selective post processing work, not so much the cpu speed himazu [3:14 PM] I see it should be a trial and error process peterthoeny [3:15 PM] i created 3 different types of hdr images from 3 raw exposures, did lens correction on them, then selectively merged them with layer masks, then fixed the curves, then fixed the color balance selectively on the image so the manual work is time consuming himazu [3:16 PM] ah peterthoeny [3:16 PM] and fun! (edited) himazu [3:16 PM] not necessarily trial and error peterthoeny [3:16 PM] a way for me to wind down before going to bed himazu [3:16 PM] sounds like a lot of work peterthoeny [3:17 PM] yes, it is, and it’s fun other people like knitting… himazu [3:17 PM] I knit when I was in high school peterthoeny [3:18 PM] really? himazu [3:18 PM] only for several months peterthoeny [3:18 PM] at home we had a mechanical knitting machine himazu [3:18 PM] in one winter peterthoeny [3:18 PM] i tried it as a kid time check: +19min it looks like @haj is not joining today himazu [3:19 PM] yep peterthoeny [3:19 PM] informal meeting or per agenda? himazu [3:19 PM] informal peterthoeny [3:19 PM] ok i don’t have much to report himazu [3:20 PM] same here peterthoeny [3:21 PM] looking at codev web, plugins web, and bugs web, no changes one update in plugins web is a nop change (edited) on twiki.org, we still have the intermittent mail issue for some users the registration fails due to mail issue i pinged the isp, will do again i need to follow up on security items, still pending anything on your side? himazu [3:24 PM] no peterthoeny [3:25 PM] how is overall twiki usage at work, stable? up? down? (edited) himazu [3:25 PM] it’s stable but I constantly get novice questions peterthoeny [3:26 PM] i have one client who is regularly coming back with new requests it is a client specific twiki app for sales order tracking so they need new functionality over time (edited) himazu [3:26 PM] the numbers of webs and pages are still increasing peterthoeny [3:27 PM] nice i have nothing else today shall we close the meeting early? himazu [3:29 PM] now 1.4 M topics or so yes peterthoeny [3:29 PM] wow! himazu [3:30 PM] 14k webs including subwebs 1.3 M page views per month peterthoeny [3:30 PM] at the time you wrote the success story it was 500k topics so a nice uptake http://twiki.org/cgi-bin/view/Main/TWikiSuccessStoryOfMorganStanley himazu [3:31 PM] 450k topic updates 110k file uploads per month 6.6k unique contributors peterthoeny [3:32 PM] that is impressive! himazu [3:33 PM] the majority of page views and updates are by robots peterthoeny [3:33 PM] btw, i learned and implemented load balancing using nginx reverse proxy himazu [3:33 PM] I understand that’s a sign of maturity oh cool peterthoeny [3:33 PM] something we could use for twiki as well himazu [3:33 PM] load balancer products are linux boxes. peterthoeny [3:33 PM] this was not twiki specific, but could be used himazu [3:34 PM] and google and other big players are probably using their own based on linux peterthoeny [3:34 PM] at a client i wrote a heavily used node.js based web app with mongodb in backend at times used by hundreds of people on a friday afternoon himazu [3:35 PM] sounds interesting peterthoeny [3:35 PM] so the system was slow always on friday afternoons himazu [3:35 PM] i’m too busy with managerial work these days peterthoeny [3:36 PM] the webserver is quite powerful, could handle the traffic based on memory and cpu cores the bottleneck was the single threaded node.js app so now it still is all on a single webserver, but load balanced actually process balanced himazu [3:36 PM] I see peterthoeny [3:37 PM] nginx is the reverse proxy, requests come in over port 443 himazu [3:37 PM] I wonder if it’s possible to do fast_cgi kind of thing with node.js peterthoeny [3:38 PM] nginx handles that over to port 8090 which is the nginx-based load balancer traffic on port 8090 is then distributed over 8 other ports 8091 to 8098 himazu [3:38 PM] maybe the end result is the same using reverse proxy or multiple node.js under a single web server peterthoeny [3:39 PM] each of those is a node.js app, all identical except for the port they are listening to yes, for twiki, the idea is to use fast cgi, and hand over the work to multiple twiki instances himazu [3:40 PM] maybe that’s the way with nginx while with apache, you have forked processes handling traffic peterthoeny [3:40 PM] since twiki is cpu and io intensive, and actual load balancing with multiple backend webservers is likely better himazu [3:41 PM] maybe peterthoeny [3:41 PM] nginx scales very nicely, little memory and cpu used if there are many requests pending ok, shall we close the meeting? himazu [3:42 PM] yep peterthoeny [3:42 PM] ok, tty next time! i’ll post the logs and minutes (edited) himazu [3:43 PM] ttyl