Open Event Website Generator https://github.com/fossasia/open-event-wsgen/
I reviewed #2353, do have a look, now it seems fine to go with. Also whom all should I be tagging who are working as an active maintainer to the repositories?
Also, I was going through #2125, the intended solution is what'd enable autocomplete [by browser, as shown in https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/url], right? or is it desired from a data source?
?
Hey, is anyone aware of this error on development-version? Can someone please help get rid of this?
1 reply
@iamareebjamal @mariobehling 1 week ago there s no review so, plz can you review ??
it throws error, I've windows 10
you need to manually install redis for windows10
just google it
i have node js
as when i do node -v on my cmd it shows
as when i do node -v on my cmd it shows
just a sec
here it is
on cmd just write "npm start"
redis server was required to be started and it seems it is working as you received pong
we are not supposed to use redis cli
ok
is this supposed to happen?
open-event-wsgen
ok ok
i think its working
@iamareebjamal I am trying to figure out the issue which we were facing when wsgen was hosted on free dyno frompast two days. Here are the things which I have found out :-
- There is a sudden increase in ram usage whenever there is a pingTimeout.
- The wsgen server doesn't respond while the resizing task is running since it is being run on the speaker images directory using the async library (async.each), all theresources get busy and the main thread gets blocked due to which server doesn't respond to any request even the regular interval ping request to maintain the socket connection. Thus the socket disconnects on pingTimeout.
- For the above thing I tried out 2 things, tried increasing the pingTimeout to 60sec from 25sec(default). The issue of timeout get resolved but in the meantime if any other get request comes the main thread doesn't respond. So then I kept the pingTimeout the same and used async.eachLimit with 2 as the limit instead of async.each which had no limit. It solved the issue.
Another thing I have noticed is that, the ram usage is pretty high and it doesn't scale down after one task generation is complete. It remains the same. This thing made me look if there is memory leak in the application. I used --inspect to load the nodejs debugger but the application heap memory do scale up to ~50MB when there is a genaration event but it scales down to normal ~37MB as well when the generation of website is complete.
When a request of website generation is there it hits 300MB and doesn't scale down and keeps scaling up on subsequent requests