Recent content by russellO

  1. R

    c# multithreading and resource locks

    If you do go the async route, you can do something like this in .Net Framework (not tested as I have to shoot): public static async Task WriteToFileMessageThreadAsync(string meterNumber, string message) { var data = string.Concat(Environment.NewLine, DateTime.Now.ToString(), message)...
  2. R

    c# multithreading and resource locks

    You can always take a look at the IL generated code for your code when using "Await". It generates a lot of code that uses a state machine to bring the processing back into the function after the awaited Task is completed. It DOES NOT sit there blocking processing. It releases the thread back...
  3. R

    SADV PE

    Last few days I can't do a tracert via ICMP or UDP anymore. Directly from the Calix router/ONT:
  4. R

    SADV PE

    Hops Time 1 Time 2 Time 3 1 bras-res-sh-plat-41-242-168-10-cpt.sadv.co.za (41.242.168.10) 27.786 ms 23.317 ms 22.782 ms 2 41.242.168.1 (41.242.168.1) 23.243 ms 22.737 ms 22.995 ms 3 cloudflare.ixp.capetown (196.60.70.198) 26.383 ms 24.542 ms 36.169 ms 4 1.1.1.2 (1.1.1.2) 22.860 ms 24.072...
  5. R

    SADV PE

    Hops Time 1 Time 2 Time 3 1 bras-res-sh-plat-41-242-168-10-cpt.sadv.co.za (41.242.168.10) 20.536 ms 11.184 ms 10.963 ms 2 41.242.168.1 (41.242.168.1) 12.802 ms 10.923 ms 10.855 ms 3 cloudflare.ixp.capetown (196.60.70.198) 11.928 ms 12.019 ms 12.071 ms 4 1.1.1.2 (1.1.1.2) 11.261 ms 11.337...
  6. R

    SADV PE

    Hops Time 1 Time 2 Time 3 1 bras-res-sh-plat-41-242-168-10-cpt.sadv.co.za (41.242.168.10) 18.784 ms 10.789 ms 11.027 ms 2 41.242.168.1 (41.242.168.1) 11.314 ms 11.582 ms 11.065 ms 3 cloudflare.ixp.capetown (196.60.70.198) 12.425 ms 18.203 ms 11.702 ms 4 1.1.1.2 (1.1.1.2) 10.992 ms 11.305...
  7. R

    SADV PE

    Thanks man. I'll continue to monitor it and report back if/when things change. I see "Vodacom in discussions to buy Vumatel and DFA" so things could change again. I assume good ol PE would be last to be integrated and optimised into the red beast.
  8. R

    SADV PE

    Hops Time 1 Time 2 Time 3 1 bras-res-sh-plat-41-242-168-10-cpt.sadv.co.za (41.242.168.10) 19.645 ms 17.836 ms 16.814 ms 2 41.242.168.1 (41.242.168.1) 17.327 ms 17.107 ms 17.065 ms 3 105.22.65.145 (105.22.65.145) 17.320 ms 17.009 ms 17.207 ms 4 ce-0-2-0-0.cr-01-cpt.za.seacomnet.com...
  9. R

    SADV PE

    Hops Time 1 Time 2 Time 3 1 bras-res-sh-plat-41-242-168-10-cpt.sadv.co.za (41.242.168.10) 18.944 ms 17.402 ms 17.159 ms 2 41.242.168.1 (41.242.168.1) 17.072 ms 17.684 ms 17.094 ms 3 cloudflare.ixp.capetown (196.60.70.198) 18.155 ms 17.675 ms 17.993 ms 4 1.1.1.2 (1.1.1.2) 17.096 ms 16.883...
  10. R

    SADV PE

    Hops Time 1 Time 2 Time 3 1 bras-res-sh-plat-41-242-168-10-cpt.sadv.co.za (41.242.168.10) 58.961 ms 57.837 ms 61.023 ms 2 41.242.168.1 (41.242.168.1) 61.286 ms 60.926 ms 59.716 ms 3 cloudflare.ixp.capetown (196.60.70.198) 64.090 ms 64.153 ms 59.157 ms 4 1.1.1.2 (1.1.1.2) 59.144 ms 59.014...
  11. R

    SADV PE

  12. R

    SADV PE

    WhatsApp from a Vumatel technician: "Hi. I spoke to our Networks today and they have advised that in P.E we are having capacity issues that is affecting all customers connected to the PE node. A lot of other customers are also having issues with speed. unfortunately there is nothing much that...
  13. R

    SADV PE

    Older ones from August 12: 1 gt-tris-bras1.sadv.net.za (41.222.138.19) 35.993 ms 30.815 ms 30.132 ms 2 gt-tris-cr1-sfp1-2.sadv.net.za (41.222.138.4) 30.315 ms 29.737 ms 29.920 ms 3 gt-tris-br2-sfp8-2002.sadv.net.za (41.222.139.103) 33.534 ms * 29.940 ms 4 pch-1.jinx.net.za...
  14. R

    SADV PE

    Here are some images I sent to SADV on 3 September after 15:00:
  15. R

    SADV PE

    Cloudflare and Google USED to be +-20ms on SADV. On Frogfoot it was 12-15ms. SADV used to go from PE -> JHB at +-20ms. Frogfoot used to go PE -> CPT at 12-15ms. I only started using Quad9 a few months back but I'm pretty sure it was also around the 22ms on SADV. Those tables are terrible...
Top