W3C home > Mailing lists > Public > public-media-capture@w3.org > October 2012

RE: recording proposal

From: Josh Soref <jsoref@rim.com>
Date: Fri, 26 Oct 2012 19:03:22 +0000
To: Media Capture <public-media-capture@w3.org>
Message-ID: <957F1ECDA90E004B8DBDE23CFC94E3A33A59DE57@XMB103ECNC.rim.net>
Harald wrote:
> Garbage collection doesn't collect memory that you have explicit
> references to, does it?

It doesn't.

> At 2 Mbits/sec, 0.4 Mbytes/sec, it would probably take you a few minutes
> to run out of memory (~5 hours for 8G of RAM, actually, unless I slipped
> a decimal).
> That's completely OK with me. You asked for it, you got it.

Assuming my math isn't terrible, this is 1.4GB/hr.

I'd like to point out that many systems use 32bit processes in which case the entire usable application address space is 2gb (that includes the app and its overhead).

Your UA+Libraries+application are probably going to consume ~100mb, on top of the first hour of recording (1hr * 1.4GB/hr), which means that there's probably another .5GB available, rounding that gives you perhaps another 20minutes [1hr * (1/(1.4 [GB/hr] / .5 [GB] ~= 1.5/.5) ~= 1/3)].

That means you have 80minutes, which is unfortunate if you're trying to deal with a 90 minute conference call (which conveniently is the length of the MC TF calls).

Note that actually running a web browser in 64bit world tends to cause it to waste more memory (because the pointer size generally doubles, and browsers use *lots* of pointers), so even if a mobile device could use 64 bit memory blobs, the UA wouldn't want to (it's better off using multiple processes).

I'm sorry for the delay, I've been worrying about other things.

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Received on Friday, 26 October 2012 19:03:56 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:02 GMT