 November 17, 2014  595 views, 444 downloads,  6 comments |
|
Firefox 33.1 (filesi.dynu.net) ...
|
|
 
# New
* Forget Button added
* Enhanced Tiles
* Privacy tour introduced
* Adding DuckDuckGo as a search option
|
|
http://www.filehippo.com/download_firefox/download/e5c86d229c3cf3f9a9e5b1e1455ab128/
|
--------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------
 Comments 6
« Nazaj
1 2
Naprej »
 |
ID345  Guest
November 17, 2014
i used to use firefox and was great for slow connection. 2 things i hated was to install extra flash for its youtube support and that address bar is not as fast as chrome as alternate to search engine. |
|
|
|
ID344 Guest
November 17, 2014
youtube video playback is very choppy on firefox.. also the videos are very soft.. |
|
|
|
ID343 Guest
November 17, 2014
Thank you for taking time to write such a very clear and informative response to my question, it was a good read. |
|
|
|
ID342 Guest
November 17, 2014
TL;DR - Firefox has to compress and encrypt your messages, including images, before it sends them to FB. The larger the file size of the image, the more effort needed from the browser. Try resizing the images and save them as either JPG or PNG files before uploading them. If you still see problems after that, consider updating the relevant software and acquiring a modern CPU.
I don't use Facebook much these days and have never needed to upload a picture through their chat system, but I can already tell you all browsers would have to do some heavy lifting to send an image like that. Facebook uses TLS to send encrypted information back and forth between server and client, as it should, but that means everything must be encrypted before sending it to FB's server. Also, to use less bandwidth and deal with fewer packets, sites and browsers commonly compress data before its sent. Both of these actions are quite taxing. In fact, they are often used as a sort of benchmark for modern CPUs, the competing numbers being how many MB worth of data x CPU can compress or encrypt per second. You may not notice any lag or a high load on your processor when sending text back and forth to your friends, but that's because text is relatively easy and quick to compress and encrypt. That is, even though replying "lol" goes through roughly the same routines of compression and encryption, you're only requesting 3 bytes of info to be sent, whereas jumping through the same hoops with a 3 MB image (over 3 million bytes of data) is going to take significantly more time and resources. Speaking of resources, it's worth mentioning that older processors are significantly less powerful than the CPUs released in the last couple of years. Some processors even have hardware accelerated encryption. Firefox (many modern, well coded programs too) can also take advantage of multicore architecture, using multiple threads to complete tasks faster. If you have several cores in your CPU, it's actually a good thing to see spikes in CPU load because it shows several cores working to get the job done faster. I mean, my processor has 4 physical cores, 8 virtual ones from multithreading, and when I see some processes chewing up 12-13% CPU in Task Manager, I can see that only a single core is being used. That means that whatever is up 100% of 1 core will take much longer than if the process used all 8 cores at about 80% capacity. It's a major bottleneck whenever that happens.
Anyway, for a browser, which is normally optimized to decrypt, extract/decompress, and render items as fast as possible, working these algorithms in reverse can (and often does) require additional CPU cycles and memory than you'd otherwise see in traditional browsing. On top of that, the images you send can cause abnormally high CPU usage due to the amount of data Firefox has to work with; that is, the size, quality, and format of your images may be causing the CPU spikes. Sending a 1920 x 1080 image is drastically different than sending an 800 x 600 image. The quality (32-bit, 24-bit, or 8-bit / 0 - 100 JPG quality / dithering) plays a great role in file size, as well as what format the image is in, the common ones being JPG, PNG, GIF, and BMP.
I played around with a screenshot I took from EVE Online. There's plenty of complexity to the image, meaning its not as easy to compress, but since I saved it in a format that does not distort the original image, I could transform it into different formats and sizes to see what happens. Both Bitmap and PNG were using 24-bit spectrums and JPG used 90% quality.
1080p Screenshot
BMP - 6 MB
PNG - 2.9 MB
JPG - 490 KB
720p Resolution
BMP - 2.6 MB
PNG - 1.3 MB
JPG - 205 KB
This demonstrates why JPG images were (and still are) so common when bandwidth and other resources is limited or when there are many, many images to load in short order (like thumbnails in an image gallery). However, since the JPG format distorts image quality with artifacts, PNG has been widely adopted as the go-to format for sites that want to maintain high quality images used in backgrounds, banners, and even icons and buttons. PNG can also include Alpha (or transparency) in an image so they can blend in with the desired background. Bitmaps, however, are basically uncompressed images to make certain there is no loss of fine quality -- they're really large and don't come with any features, but there is a large portion of internet folk who either don't know or don't care about formats and file sizes. If you're one of those people by the way, you better get used to hot CPU temps and long wait times while uploading pictures to FB and other sites.
All in all, Firefox has a lot of work to do when uploading images through secure connections. The best thing you can do to lessen the work is to be responsible on the interwebs. If you want to share a photo you just took with your 60 megapixel camera, open it up in an image editor like Paint.NET (free) or Photoshop and resize it to a reasonable resolution (1920 x 1080 is considered full HD and fits perfectly on a 1080p monitor and 1280 x 720 is standard HD, looks great on any modern smartphone), and save that photo in PNG if fine-quality matters, like for small text, or JPG if it's just a selfie. THAT will help you upload pictures faster and put less stress on your processor.
One last thing. Make sure the relevant parts of your system are up-to-date, as out-dated software can lead to bugs and memory leaks. This means making sure your OS (typically Windows) is fully updated along with Firefox and plugins like Flash, Silverlight, and Java. Any number of plugins can be used to expedite the compression, encryption, and transmission of images, and it only takes one glitch or poorly written code to throw a wrench into the whole uploading process. |
|
|
|
ID341 Guest
November 17, 2014
Anyone else getting high CPU usage with Firefox when uploading files to a Facebook conversation? |
|
|
There are no comments ......
« Back
1 2
Next »
 Note:
Guests comments are allowed ...
|
|
|
|
|
|
|
|
|
