5 ms·

I'm confused why it would take any time at all to find a match. Sounds fun and weird and a little awkward, just how the internet should be. But I can't seem to

I'm confused why it would take any time at all to find a match. Sounds fun and weird and a little awkward, just how the internet should be. But I can't seem to be matched with anyone.

openknot 5y ago
Yes, I've been waiting (still on) for about 10 minutes so far on Chrome (adblock disabled) to ensure browser compatibility. I started a timer for a different task at around the same time the wait started, so this measurement is fairly accurate. Update 1: A match didn't occur yet, 30 minutes total wait time. Update 2: Still no match. I entered the wait room for the original submitted link and left the tab open for 30 more minutes in the background (2:48 pm ET to 3:18 pm ET), with unmuted headphones on. 60 minutes total wait time across sessions.
amadeuspagel 5y ago
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.

I'm confused why it would take any time at all to find a match. Sounds fun and weird and a little awkward, just how the internet should be. But I can't seem to be matched with anyone.

openknot 5y ago

Yes, I've been waiting (still on) for about 10 minutes so far on Chrome (adblock disabled) to ensure browser compatibility. I started a timer for a different task at around the same time the wait started, so this measurement is fairly accurate. Update 1: A match didn't occur yet, 30 minutes total wait time. Update 2: Still no match. I entered the wait room for the original submitted link and left the tab open for 30 more minutes in the background (2:48 pm ET to 3:18 pm ET), with unmuted headphones on. 60 minutes total wait time across sessions.

amadeuspagel 5y ago

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.