|
|
Posted by Steve on 04/24/07 13:15
"lawrence k" <lkrubner@geocities.com> wrote in message
news:1177399960.262143.155740@c18g2000prb.googlegroups.com...
| On Apr 16, 1:40 pm, "Steve" <no....@example.com> wrote:
| > "lawrence k" <lkrub...@geocities.com> wrote in message
| >
| > news:1176742297.641577.63900@y80g2000hsf.googlegroups.com...
| > | On Apr 16, 10:29 am, tasteless <tastel...@gazeta.pl> wrote:
| > | > Hi guys,
| > | >
| > | > I need really hard questions (about 10) about PHP programming (some
of
| > | > elements OOP as well, but no MySQL questions - this is different
part),
| > | > this questions needs to be very hard, but the experienced senior PHP
| > | > developer should answered on it.
| > |
| > | Which causes a bigger surge in memory usage, including() a file with a
| > | large array or unserializing the same information after its been
| > | serialized?
| >
| > good one...i'd love to know the correct answers for these. my guess
would be
| > a higher spike when unserializing.
|
|
| Read this:
|
| http://doughboy.wordpress.com/2007/02/28/big-arrays-in-php/
did you see joel's comment at the bottom? using 5.2, there was no
difference - arrays are copy-on-write. the test was done in php 4.x.
that was interesting though. i use arrays a lot. i'm suprised that even in
4.x they consumed so much memory.
Navigation:
[Reply to this message]
|