Custom feed, not possible

Discussion in 'Feeding' started by angel, Aug 5, 2018.

  1. James

    James Guest

    As a bonus though - -this new VRS might be buggy as the leaflet maps are new. You guys can report issues to Andrew at virtualradarserver.co.uk
     
  2. MDA

    MDA Administrator Staff Member

    Not very nice but should not affect VRS instance. IMO main problem is that feeder migration from old version is not fully finished. If you send me VRS web admin login/password and receiver list (of course as PM) I can review and update.
     
  3. James

    James Guest

    The plan is to add 2-3 more custom feed servers. Then write something to pull stats for you guys.

    Also is anyone good with bash or python and netstat. I need a script to map IP from proxy server and get what port it is sending 30005 connections to on the backend. Then we can request data from the server and port to show on the dashboard.
     
  4. Jhonny Monclair

    Jhonny Monclair Active Member

    Lol, I didn't notice at all the brand new links to new servers...we're getting too old!
     
    MDA and James like this.
  5. James

    James Guest

    It's all complete. All that happened is instead of all ports from 51000 to 53099 sent to one server.

    51000-51150 sent to customglobal
    51150-5299 sent to customglobal2
    53000-53099 sent to customglobalvrs

    I copied over config from original custom feeds server into each of the three.
     
    Rubiconic and MDA like this.
  6. James

    James Guest

    So as a future refference even with threading and some fancy optimizations VRS tops out at about 150 feeds. After that the main thread can't handle what's going on and chokes.
     
  7. MDA

    MDA Administrator Staff Member

  8. James

    James Guest

    Something fun.

    Customglobal2 is using 15Ghz, 8 cores, to do whatever it's doing.
     

    Attached Files:

    Jhonny Monclair likes this.
  9. James

    James Guest

  10. James

    James Guest

  11. MDA

    MDA Administrator Staff Member

    I wanted to see Jhonnys feed :D
     
    Jhonny Monclair likes this.
  12. James

    James Guest

    uhhh ... LOL ... I don't know what port he is .. But it's there lol ... god I hope it's there ...
     
    Jhonny Monclair likes this.
  13. MDA

    MDA Administrator Staff Member

    And to see my data I need to restart VRS, looks like bug in new VRS version.
     
  14. James

    James Guest

    There are a bunch of bug reports. I'll keep these updated to the latest VRS as he pushes out fixes.

    I can't get it to run stable on linux/mono 5.x .. only 4.6.2


    I need to edit the config for the 2nd custom feeds server to remove all the other ports. I'll do that now.
     
  15. Jhonny Monclair

    Jhonny Monclair Active Member

    A big improvement...before the migration, visualization was laggy, routes of selected planes
    took many seconds to appear, now I can feel the new gear, it is reactive!
    Thanks guys, good job!

    btw, one of my feeders is on 51154, another one is on port 51005 (but silent at moment, under maintenance)
     
  16. James

    James Guest

    You should be guilt stricken lol

    Those unused ports get lonely!
     
  17. MDA

    MDA Administrator Staff Member

  18. James

    James Guest

    "I need to edit the config for the 2nd custom feeds server to remove all the other ports. I'll do that now."

    :)
     
  19. MDA

    MDA Administrator Staff Member

    If you want I can help.
     
  20. James

    James Guest

    Thanks! It's done. :)

    For some reason and maybe this is .NET and MSFT or a choice by VRS dev. But if you edit things - it changes the UI on every keystroke. Because .NET or VRS is inefficient -- makes it impossible to edit using options. Type too fast and it freezes and crashes VRS.

    I have to edit the XML file in a text editor then reboot VRS. Saves time, sort of.

    This includes the WebUI. Anything over a few feeds and updating config takes a minute or 2 to update. Makes WebAdmin useless.

    I sharded the custom feed servers because reboots were taking 30 minutes.