In revision 6134 the .exe size was 6.4 MB for the 32 bit version and 7.3 MB for the 64 bit, but in 6136 more than double their size and they are now 13.7 MB and 18.3 MB, why? Code changes doesn't seem to justify that size change.
Thanks.
In revision 6134 the .exe size was 6.4 MB for the 32 bit version and 7.3 MB for the 64 bit, but in 6136 more than double their size and they are now 13.7 MB and 18.3 MB, why? Code changes doesn't seem to justify that size change.
Thanks.
I disabled compression by UPX, testwise. The installer still has its own compression, so this only affects the nightly builds.
I have the impression that unpacking heidisql.exe always takes some notable milliseconds.
And with the speedy internet nowadays it does not make a great difference when downloading, does it?
And with the speedy internet nowadays it does not make a great difference when downloading, does it?
Depends on how often you go through this procedure each day. Usually update takes no more than 10 seconds and it is OK. Sometimes connection may be slower or system may be loaded so that update takes little more time. It could be easily solved though. You could add command line argument to update HeidiSQL so that anybody can create task in scheduler which will update HeidiSQL each night.
I'd say about 20Mbps is currently the average bandwidth for local traffic. But the issue is more that connection to European or North American servers require a lot of hops, and there is sometimes some congestion on the international pipes.
The download is by no means unbearable. I just noticed that the file is now much bigger and wondered why.
Next time there's a nightly upgrade, I'll try to do a screen capture.
Let me just clarify... internet providers can give a lot more than 20Mbps to consumers. Consumers have to choose a bandwidth package, and generally they choose anywhere from 4Mbps (my father-in-law) to 50Mbps. That's why my guess is that the average consumer package is around 20Mbps.
Please login to leave a reply, or register at first.