browser RAM

[rj]

http://rackjite.com

Been giving them what they want to get the traffic. As such the blog has become an embedded video server!
Whatever works don't ya know...

So I got it at 10 articles and did some tweaking to get some sizes down as best I could. Running 107k load up which isn't too bad... The slowdown problems seem only to come up when the embedded servers are having trouble.

BUT...
I go to Taskmanager/processes and find that IE and FF on my page suck up almost 300 megs.
Most other multimedia pages are between 80 and 150megs.
So how does that affect things?

If my blog ate up your ram, wouldn't the browser have to go to the HD and slow things down? A lot? Or not so much? And what do you think the RAM of the user computer would have to be to be hurt by this issue?

[garvinhicking]

Hi!

You can use Firefoxes Firebug or Google Chrome for example to introspect usage/allocation of memory.

Your presumption is correct: If a lot of data is shown on a webpage, the browser first allocates RAM, and if that does not suffice, swaps out to RAM.

Currently your blog seems to autoload files from msnbc.rd.llnwd.net which is not reachable for me, so I cannot complete the analysis. But until then,
already 108 requests were made on your page, loading a total of 1MB of data and taking 22 seconds to load.

108 requests is an awful lot. I can only advise to not spawn so many auto-loading videos. I believe there are ways to use javascript embeds
that do not autoplay media, but only start when mouseover effects are enabled. This is called "lazy load" and much more friendly to the user, because only the data is loaded that is interesting for him.

Regards,
Garvin

[Don Chambers]

When I first hit your page, it made 132 requests and downloaded 3,386K of data!!! Most of that was in flash objects (1,629k) and images (1,490k).

In addition to Garvin's recommendation, you could also have fewer entries per page, and possibly consider using only a still image in your entry body, and moving the embedded flash content to your extended body, so visitors have to click another page deep to see it. This could a) boost your pageviews or b) annoy some users who are used to seeing everything on the frontpage only, rarely navigating deeper into the site.

[rj]

Been testing speed all over the place for a few months now... Cable loads a doable blog in a few seconds, but then as you say, about 20 more to finish off filling in the videos...

The embedding I have always been a bit unclear about. I looked at each individual video article and get about 100megs of usage no matter YOUTUBE, MSNBC or COMEDYCENTRAL. Its not one or the other its video embedding.

I thought... The embed code makes it go to the video server, grabs the get ready code, the player and the jpg of the player... This shows as adding about 60K per video.
I dont think it uploads the video flv file. It just gets it all ready for someone who may or may not click the play button on the player and then streams it from the source server... Because I know I don't pay GODADDY for embedded video usage... But do when I serve my own FLV in my own player.

I cannot change what I do. I am finally making a little money...
I could capture it all and serve them myself easy enough, other than the time involved in converting them from flv to edit, editing, and then converting them back to flv to play. It would cost me at godaddy but it sure would speed things up!

Another thought was to play a video I want to use. When It shows what I like, print screen, photohop, crop it, size it, jpg it and then put it up on the blog as graphic link to the URL of the video... But they go off site then.