<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="DE" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Yes, if their platform becomes even moderately successful, the load will likely exceed how much their shiny can handle. I warned them in the call about it, but they did not seem particularly
interested.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">It could be that Posit’s managed shiny server costing thousands of dollars a year performs better than the free ShinyProxy middleware that we use for CollEc. Yet, even with the paid
service the app is unlikely to meet the requirements and come anywhere close to a more professional setup.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I understand why people use shiny apps. I use them myself. If you have a data science background, it is way easier to build an app with shiny than it is to build it with NodeJS. Shiny
apps are convenient way of letting users explore a data set or a method. And in an environment with frequent staff turnover where people usually do not have a web development background, like at an economics department, maintenance is easier to ensure with
a shiny app than with a more complex structure.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I built an entire teaching platform in shiny and am fed up with that tool. Its poor performance, hidden reactivity layer, and limited capabilities make it annoying to work with in apps
beyond simple data or method illustrations. So, my new colleague and I are currently transitioning to a React/ Next.js/ Deno/ Redis/ PostgreSQL stack. Doing that besides research, teaching, R package development, software development for the institute and
university, other institute duties, and personal affairs means that it takes at least a few months until I will have time to rewrite CollEc.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">I presume it is fine to wait until then, as CollEc appears not to be very popular anyway.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:9.0pt">Christian Düben<br>
Doctoral Candidate<br>
Chair of Macroeconomics<br>
Hamburg University<br>
Germany<br>
</span><span style="font-size:9.0pt"><a href="mailto:christian.dueben@uni-hamburg.de"><span lang="EN-US">christian.dueben@uni-hamburg.de</span></a></span><span lang="EN-US" style="font-size:9.0pt"><br>
</span><span style="font-size:9.0pt"><a href="https://www.christian-dueben.com"><span lang="EN-US">https://www.christian-dueben.com</span></a></span><span lang="EN-US" style="font-size:9.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Christian Zimmermann <chuichuiche@gmail.com>
<br>
<b>Sent:</b> Freitag, 12. Mai 2023 13:53<br>
<b>To:</b> Düben, Christian <christian.dueben@uni-hamburg.de><br>
<b>Subject:</b> Re: [CollEc] Helos down<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">This is the kind of problem I foresee for the Banque de France site...<br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Christian Zimmermann<o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Fri, May 12, 2023 at 6:52 AM Düben, Christian <<a href="mailto:christian.dueben@uni-hamburg.de">christian.dueben@uni-hamburg.de</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">There had been a bunch of exited Docker containers. I cleared them. CollEc should, in the medium term, move away from shiny apps. It is well possible that the current system does not support request bursts from bots.<br>
<br>
I currently do not have time for that, but I can schedule it for the end of this year.<br>
<br>
Christian Düben<br>
Doctoral Candidate<br>
Chair of Macroeconomics<br>
Hamburg University<br>
Germany<br>
<a href="mailto:christian.dueben@uni-hamburg.de" target="_blank">christian.dueben@uni-hamburg.de</a><br>
<a href="https://www.christian-dueben.com" target="_blank">https://www.christian-dueben.com</a><br>
<br>
-----Original Message-----<br>
From: CollEc-run <<a href="mailto:collec-run-bounces@lists.openlib.org" target="_blank">collec-run-bounces@lists.openlib.org</a>> On Behalf Of Thomas Krichel<br>
Sent: Freitag, 12. Mai 2023 13:22<br>
To: CollEc Run <<a href="mailto:collec-run@lists.openlib.org" target="_blank">collec-run@lists.openlib.org</a>><br>
Subject: Re: [CollEc] Helos down<br>
<br>
Thomas Krichel writes<br>
<br>
> I can ping it, but not more than that. I can't read email while this <br>
> goes one, but you can to me at <a href="mailto:editors@nep.repec.org" target="_blank">
editors@nep.repec.org</a>.<br>
<br>
It has been up since about 7:50 UTC. Cezar rebooted. It was out of<br>
memory. I think if I had a root window open<br>
<br>
There are log entries for the oom killer<br>
<br>
root@helos /var/log # grep oom-killer kern.log May 12 03:18:06 helos kernel: [4449730.455246] systemd invoked oom-killer: gfp_mask=0x1100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 May 12 04:20:22 helos kernel: [4459782.217108] systemd invoked oom-killer:
gfp_mask=0x1100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 May 12 06:53:10 helos kernel: [4469843.887742] mutt invoked oom-killer: gfp_mask=0x1100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0<br>
<br>
The web access log, entries of today, contains 4716 entries of petalbot<br>
doing stuff like<br>
<br>
114.119.145.116 - - [12/May/2023:11:04:22 +0000] "GET /app_direct/collec_app?_inputs_&navbars=%22tab_Coauthors%22&_values_&g_author=%22ppa246%22 HTTP/1.1" 301 162 "<a href="https://ideas.repec.org/f/ppa246.html" target="_blank">https://ideas.repec.org/f/ppa246.html</a>"
"Mozilla/5.0 (Linux; Android 7.0;) AppleWebKit/537.36 (KHTML, like Gecko) Mobile Safari/537.36 (compatible; PetalBot;+<a href="https://webmaster.petalsearch.com/site/petalbot" target="_blank">https://webmaster.petalsearch.com/site/petalbot</a>)"<br>
<br>
I supect that petalbot made too many requests. <br>
<br>
<br>
--<br>
Written by Thomas Krichel <a href="http://openlib.org/home/krichel" target="_blank">
http://openlib.org/home/krichel</a> on his 21161st day.<br>
<br>
_______________________________________________<br>
CollEc-run mailing list<br>
<a href="mailto:CollEc-run@lists.openlib.org" target="_blank">CollEc-run@lists.openlib.org</a><br>
<a href="http://lists.openlib.org/cgi-bin/mailman/listinfo/collec-run" target="_blank">http://lists.openlib.org/cgi-bin/mailman/listinfo/collec-run</a><br>
<br>
_______________________________________________<br>
CollEc-run mailing list<br>
<a href="mailto:CollEc-run@lists.openlib.org" target="_blank">CollEc-run@lists.openlib.org</a><br>
<a href="http://lists.openlib.org/cgi-bin/mailman/listinfo/collec-run" target="_blank">http://lists.openlib.org/cgi-bin/mailman/listinfo/collec-run</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</body>
</html>