4 ms·

I'm using deno deploy, which is split accross 25 regions, so you have to match with someone from the same region. (I tried to use my own server at first, but it

I'm using deno deploy, which is split accross 25 regions, so you have to match with someone from the same region. (I tried to use my own server at first, but it crashed, so I switched to deno deploy in a hurry, without having figured out how to connect it accross regions.)

em-bee 5y ago
seems the many regions spread the potential users to thin. you probably want a stronger single server because connecting chats across multiple servers only makes your code more complex when your actual problem seems to be that you just need more ram or cpu. alternatively consider using existing platforms like jitsi. the benefit of your site is not the implementation of the audio channels but the ability for HN users to find each other. you could create a frontend where HN users join but are redirected to a jitsi room once they are matched. unless of course part of the point is for you to experiment and learn webrtc and related technologies...
- amadeuspagel 5y ago
  > seems the many regions spread the potential users to thin. you probably want a stronger single server because connecting chats across multiple servers only makes your code more complex when your actual problem seems to be that you just need more ram or cpu. I checked ram and cpu with top when I was using a VPS, and it was basically nothing. (I didn't monitor it continuously, so maybe that was still the problem.) But you're right in principle, I should use one server. > alternatively consider using existing platforms like jitsi. the benefit of your site is not the implementation of the audio channels but the ability for HN users to find each other. But once people found each other, it's webrtc, it's p2p, so that shouldn't be a problem for the server.
  - em-bee 5y ago
    then i'd suggest to go back to a single server and find out what causes the crashes. you can keep the current version running in parallel and tell people to hit your single server for testing.

em-bee 5y ago

seems the many regions spread the potential users to thin. you probably want a stronger single server because connecting chats across multiple servers only makes your code more complex when your actual problem seems to be that you just need more ram or cpu. alternatively consider using existing platforms like jitsi. the benefit of your site is not the implementation of the audio channels but the ability for HN users to find each other. you could create a frontend where HN users join but are redirected to a jitsi room once they are matched. unless of course part of the point is for you to experiment and learn webrtc and related technologies...

amadeuspagel 5y ago
> seems the many regions spread the potential users to thin. you probably want a stronger single server because connecting chats across multiple servers only makes your code more complex when your actual problem seems to be that you just need more ram or cpu. I checked ram and cpu with top when I was using a VPS, and it was basically nothing. (I didn't monitor it continuously, so maybe that was still the problem.) But you're right in principle, I should use one server. > alternatively consider using existing platforms like jitsi. the benefit of your site is not the implementation of the audio channels but the ability for HN users to find each other. But once people found each other, it's webrtc, it's p2p, so that shouldn't be a problem for the server.
- em-bee 5y ago
  then i'd suggest to go back to a single server and find out what causes the crashes. you can keep the current version running in parallel and tell people to hit your single server for testing.