Three here all about 2.8MB and seem to have upload OK

3.74MB

lincolnMiller.jpg  7.3Mb

I’m sure others are having real problems with a couple of intermittent bugs in the image upload system, and have dug into it in so far as a moderator has access to the forum innards without success.   Unfortunately I can’t replicate the problem, which makes it impossible for me to report the bug adequately.

Everyone assumes the bug is in the forum, and it might well be, but could also be due to network issues or something adrift in the users computer.    Nick mentions time-outs due to slow network speed, and the old forum was extremely sensitive to this.   The new one less so, but slow networking remains a possible cause.

Be useful to know:

• file type and size.
• Where uploaded from, internet or PC
• Typical internet speed.
• PC model, operating system and version
• Browser and version

I’ve had bother downloading jpg images from the internet that turned out to be jpg inside webp.   The forum won’t load webp directly – members have to extract the contents and send the saved as jpg.  Webp seems to becoming common.

A related bug, may be entire posts disappearing only to return later.   This, and missing images, could be a cache problem.

Whatever the cause, it’s annoying!

Dave

Thanks Mark.

Your computer, OS, and browser are all good – therefore unlikely to be the problem.

The network is suspect though.   6mbps is the speed that caused trouble for me uploading images to the old forum making it advisable to reduce size before sending. Upgrading to a 60mbps service fixed it.   Not proved though!

I might be able to simulate a slow network tomorrow and will report back if that causes image fails.

Dave

If anyone wants to try a simple speed-check on their system, I can recommend this:

https://fast.com/en/gb/

MichaelG.

.

It is ‘powered by NETFLIX’ and the technical details are briefly explained via the ? button … with much more available in a hyperlinked blog post.

You’ve shown me yours, Jason … so I better show you mine

MichaelG.

.

Those are some pretty impressive upload speeds. Back in the day I specified 10:1 ratio target for the UK cable network though some places could only manage 20:1. We had limitations due to the modulation technique and DOCSIS 2 only using the bottom 110MHz of the frequency range. (early systems were less than half that) The early proposals didn’t realise people would create bulk content themselves so it was designed for download capacity with only little requests and acknowledgements going upstream. They certainly never expected every photo snap to be >16Mpixels.

Other relevant information might be location town/country and ISP, time of day (school kids arriving home hammer the network).

Throttling network speed is theoretically straightforward in linux, made even easier with a utility called wondershaper.   Unfortunately, in line with the golden rule ‘nothing is ever easy’,   wondershaper fails on Ubuntu, and none of the fixes I tried work.   However, wondershaper is a front-end to the ‘tc’ utiitity (traffic control), and this tc command worked:

sudo tc qdisc add dev enp4s0 root tbf rate 1000kbit burst 16kbit latency 50mS

This magic incantation means “to device enp4s0 (my ethernet network connection), add a traffic block filter that limits the maximum upload speed to 1megabits per second, with a 16kbits per second burst, and 50mS of latency (network delay).    The effect can be seen in this speedtest, where my download is just under 50Mbits/s but my upload speed is reduced from 10Mbits/s to 0.9.

When sending images to the forim, it’s the upload speed that matters, and on an asynchronous service upload is about 20% of the download speed.

My next post will contain a 7Mb image.   Not putting it this one in case my slow network mangles everything and I have to retype it.

Dave

Shows OK for me

I see Jason confirms seeing the test images correctly, and so am I.   Anyone else having any bother please say so.

To finish off if anyone wants to play with traffic control themselves, network device is identified with the ifconfig command.  Also, the changes made by tc are per session, and turned off by logging out or rebooting.   They can also be disabled inside the session by deleting the qdisc  (queue discipline) object thus:

sudo tc qdisc del dev enp4s0 root

I believe qdisc controls stack and remain active, so typing

sudo tc qdisc add dev enp4s0 root tbf rate 250kbit burst 16kbit latency 50mS
sudo tc qdisc add dev enp4s0 root tbf rate 1000kbit burst 16kbit latency 50mS

doesn’t increase speed to 1000kbit/s because the earlier 250kbit control is still running.   You have to kill it explicity:

sudo tc qdisc add dev enp4s0 root tbf rate 250kbit burst 16kbit latency 50mS  # Add 250kb qdisc filter device enp4s0
sudo tc qdisc del dev enp4s0 root         # remove all qdisc filters from device enp4s0
sudo tc qdisc add dev enp4s0 root tbf rate 1000kbit burst 16kbit latency 50mS

Dave

Hi, so I tried MichaelG’s link fairly early this morning, and got this result.

I tested it again about mid morning, and got this result.

I then did a test using Google, a little after 2pm, and got this result.

I did similar tests on a couple of other laptops, which are newer than this one, and very similar results were seen.

So how about a 4MB picture of a nice old Colchester Mastiff lathe, which took about two minute to load, with. with about a 20 second pause half way through the upload ( Sorry to those who don’t like industrial machines on here)

Regards Nick.