So, maybe we have a provider that is having saturation issues or we are not having a 100% contented to us pipe.
But how to proof? We’ve had something similar in the past and than the provider comes up with some ftp servers we can download from with ftp and off course, always we reach top speed according contract…
And maybe indeed the route to his servers is OK. How to find where other bottlenecks are to be found.
If I read the several post from other users from all over the world with good results, I’m wondering why I cannot have my contracted speeds?
Any help/suggestions from this forum is appreciated.
FYI - The free public btest server available to all Mikrotik admins is averaging just over 1.5 TB (tera-bytes) of best data a month. Wow - It looks like it gets used/tested against up to 50 times a day. And at least one person ran a 6-hour 200-meg sustained test during the last month.
I would like to ask - if anybody has the extra bandwidth capacity - would you be interested in a 24 hour sustained 1.5 gig up & down test ? I am interested in an opportunity to stress test my un-used spare capacity under heavy load.
Edit: or a bunch of testers running a 24 hour btest against me at what ever they can spare … I would then set my simple queue to limit at 1.5 gig up & down flat.
Heads up - I will be shutting down both speedtest servers in about 30-minutes from now.
They should be turned on in about 15 hours or so.
Our 10-gig fiber is being worked on - My network is going to fall back to a microwave link. To conserve bandwidth, I will temporarily shut down both speedtest servers - then bring them back on-line when the new fiber is connected.
I thought I would post this - because the btest server has many people testing it at all times of the day.
So, when it goes down, it is not you…
Kristaps,
I am able to duplicate and repeat the lockup with my ROS x86 PUBLIC btest server (hosted on a MvWare ESXi server).
I will shortly be sending an email to support@mikrotik.com
I will describe in the email how to duplicate the lockup.
What happens when the ROS locks up is the following:
No IP network access
Console & keyboard to ROS CLI is still active
Can not ping anything (including WAN IP address and also the 127.0.0.1 loopback IP address)
North Idaho Tom Jones
Thank you for the endeavor and for sharing this with the community. As a home user I must say I’m pretty happy about my speedtest results:
status: done testing
duration: 31s
rx-current: 305.7Mbps
rx-10-second-average: 306.0Mbps
rx-total-average: 197.7Mbps
lost-packets: 2740
random-data: no
direction: receive
Heads up
Starting this morning (Monday 6/20/2016 PST), I am now running the Mikrotik CHR 64-Bit version or ROS.
The original x86 ROS 32-bit btest server is turned off, while we test the 64-bit CHR ROS.
The new ROS is the following:
- Running under VMware ESXi (the same server that was hosting the 32-bit ROS btest server)
- VMXNET3 Ethernet (paravirtulized Ethernet driver in the Mikrotik ROS) for ether1 (old 32-bit was E1000E)
- 2 CPUs with 8-Gig ram (Old 32-bit ROS was 1 CPU with 2-Gig ram)
- Latest ROS version (6.35.4)
If you experience anything other than normal speeds - please let me know.
ALSO - for the Mikrotik admins with a 1-gig or faster connection, please test and let me know if you are able to send & receive at the speeds you were getting in the past. Mikrotik Bandwidth test server: 207.32.195.2
bandwidth test username: btest
bandwidth test password: btest
FYI: Below is the simple queue I was using on the older x86 32-bit ROS best server. I kept the same setting for the new CHR btest server.
I guess I am going to need to look at what kind of bandwidth the 60 day trial license can support for throughput.
In-house I was able to send to it (from another ROS 32-bit) at near 10 gig. However - I did not measure how fast the ccr can send. Is the send speed limited (when running the built-in 60 eval license -or- do I need to do something (license) to kick up the vmxnet3 Ethernet send speed ?
North Idaho Tom Jones
Almost cool.
This morning I had somebody doing a btest to my public Mikrotik ROS 32-Bit virtual hosted server at an average of 3-Gig for about one hour - and I did not even notice a difference on my network.
I just updated the public access btest server (207.32.195.2)
It is now version 6.36 (X86 ROS running as a virtual client - which is hosted on my VMware ESXi server_
I welcome the Mikrotik admins to bang away at it to help me determine if it is stable under greater than 1-gig (up to 3-gig) throughput btest loads.
Specifically I want to see if the random lockup condition has now gone/resolved under heavy loads where the simple-queue kicks in.
Hmm, for some reason I could not connect to 207.32.195.2 using BW test in MT with TCP (user btest/btest) from Serbia.
Is it just some temp issue, or is this project done with testing ?
Sorry about the can’t connect.
The problem is the x86 ROS keeps locking up.
From what I think I am seeing, it appears that if somebody continues a btest bandwidth test - and my simple queue kicks in to limit them to 250 meg - and the test continues, then sometimes the TCP/IP stack on my ROS x86 takes a dump and no longer talks. The console is still responsive but nothing IP talks. When my ROS does this, it can not even ping the loopback address 127.0.0.1 - it acts like all IP traffic is just turned off. From the console, I still have CLI commands to the ROS. To get my btest ROS server back on-line, I have to reboot the MIkrotik ROS.
North Idaho Tom Jones
