split the object to 4, but nothing changed.
var obj_num = 500;
var split = 4
var fill = [];
for (var s = split; s > 0; s--) {
fill[s]={};
for (var i = obj_num/split; i > 0; i--) {
fill[s]["fill string***" + i] = "fill string" + i;
};
}
setInterval(function (
Aha, didn't know cloud9 is dutch, seeing many familiar names there from
this group! Great product too.
Thanks guys.
By the way I'm from Den Bosch. Not much here but perhaps that means
opportunities..
Antoine
On Wed, Nov 7, 2012 at 11:33 AM, Stéphan Kochen wrote:
> Antoine,
>
> Angry Bytes
It depends if your doing some OS specific operations. The main problem
would be the way you defined your paths, but check that out on the link
Nathan posted.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You receiv
Most of you misses the point, it is sadly. Why it is preferred to have
shorter code (as long it does not add any complexity) is it because it will
make it easier to understand what is happening. That is the largest
difference between a low level programming language and a high level
programming
I attached segvhandler (https://github.com/ddopson/node-segfault-handler)
and got the following: https://gist.github.com/4039738
Looks like it is in contextify.node
If you run the tests in isolation you don't get the error. It could be down
to a overflow or leak somewhere that only shows its he
We recently upgraded from 0.4.12 to 0.8.14 (about freaking time, huh?)
and our SSL certificate checking is having some troubles with some
CAs.
We're receiving the following error when we test for 'authorized'.
"Hostname/IP doesn't match certificate's altnames"
Here's the pertinent code to reprodu
On Thu, Nov 8, 2012 at 5:18 PM, Paul Serby wrote:
> I attached segvhandler (https://github.com/ddopson/node-segfault-handler)
> and got the following: https://gist.github.com/4039738
>
> Looks like it is in contextify.node
>
> If you run the tests in isolation you don't get the error. It could be
On Thu, Nov 8, 2012 at 5:38 PM, Shawn Parrish wrote:
> We recently upgraded from 0.4.12 to 0.8.14 (about freaking time, huh?)
> and our SSL certificate checking is having some troubles with some
> CAs.
> We're receiving the following error when we test for 'authorized'.
>
> "Hostname/IP doesn't ma
We thought that might be the case but the checks work fine in 0.4.12,
are seen as valid by all major browsers as well as curl, like you
said. Some Thawte certs which I believe are valid are also failing
with this error message.
I'm pretty sure the error is incorrect as the hostname matches.
Any
On Thu, Nov 8, 2012 at 6:28 PM, Shawn Parrish wrote:
> We thought that might be the case but the checks work fine in 0.4.12,
> are seen as valid by all major browsers as well as curl, like you
> said. Some Thawte certs which I believe are valid are also failing
> with this error message.
>
> I'm
On Thu, Nov 8, 2012 at 10:34 AM, Ben Noordhuis wrote:
> On Thu, Nov 8, 2012 at 6:28 PM, Shawn Parrish wrote:
>> We thought that might be the case but the checks work fine in 0.4.12,
>> are seen as valid by all major browsers as well as curl, like you
>> said. Some Thawte certs which I believe ar
Thanks chaps; consider that can of worms well and truly opened :)
I didn't come across segvhandler when I was searching for info - looks very
handy!
Cheers,
G.
On Thursday, November 8, 2012 4:39:52 PM UTC, Ben Noordhuis wrote:
>
> On Thu, Nov 8, 2012 at 5:18 PM, Paul Serby
> >
> wrote:
> > I
Hi i wrote my binding.cc and binding.gyp for my ARM library,
I compiled and i always see the below error,
bash-4.1$ sudo
/home/pavincoll/Downloads/node-v0.8.0/deps/npm/bin/node-gyp-bin/node-gyp
configure build
[sudo] password for pavincoll:
gyp info it worked if it ends with ok
gyp info using no
I have a script which sets all the Variables pointing to the ARM File
system and Compiler to ARM.
On Thursday, November 8, 2012 2:13:34 PM UTC-8, Pavi wrote:
>
> Hi i wrote my binding.cc and binding.gyp for my ARM library,
> I compiled and i always see the below error,
> bash-4.1$ sudo
> /home/p
Pauses that follow initialization will actually become much smaller
(given that you disable idle notification that are abused by node).
Pauses during initialization of your test are irrelevant because your
allocation rate is not at the realistic level.
It is highly unlikely that your application
On Thu, Nov 8, 2012 at 11:13 PM, Pavi wrote:
> Hi i wrote my binding.cc and binding.gyp for my ARM library,
> I compiled and i always see the below error,
> bash-4.1$ sudo
> /home/pavincoll/Downloads/node-v0.8.0/deps/npm/bin/node-gyp-bin/node-gyp
> configure build
> [sudo] password for pavincoll:
I'm not focus on the initialization time, but GC impact in large memory
usage cases.
In the test case, I used 850MB memory, which is normal for a net server
application, the GC takes 5*450ms and 2*3050ms periodically(every tens of
seconds).
I think there should be some way to imporve it.
At leas
No I mean how "foo()" within a class method may be another method
call, global function etc, extremely lame "feature"
On Nov 8, 7:58 am, Fredrik O wrote:
> Most of you misses the point, it is sadly. Why it is preferred to have
> shorter code (as long it does not add any complexity) is it because
18 matches
Mail list logo
