Re: [nodejs] Re: best practice for real-time socket-based cross clustered-process data communication and computation
Thanks Johnny, dnode is very inspiring. cluster2 may help us a lot in production! Regards, ty 2012/9/11 Johnny Honestly mostmodern...@gmail.com I heard about this cluster manager today directly from the guys at ebay working on ql.io https://github.com/ql-io/cluster2 You can stream buffers from parents to child process using stdin/out If you need sockets try dnode https://github.com/substack/dnode On Monday, September 10, 2012 1:45:12 AM UTC-7, Yi wrote: Hi node mates: I'm looking for your advice about how to design and implement an mechanism for real-time socket-based cross clustered-process data communication and computation. [The server layout] clientA --tcp socket-- node service A -- DataModelA -- unique radis data store clientB --tcp socket-- node service B -- DataModelB -- unique radis data store * node service A and B are cluster on the same server * 1 data model represent 1 client at the run time * both node service A and B talk to the same redis data store [The function request] I need to implement a mechanism, in which: 1. clients in difference processes can communication with each other efficiently. 2. there need to be a centralized place for data computation base on data models represents difference clients the logic looks like the following diagram: clientA --tcp socket-- node service A | socket pipe | v clientB --tcp socket-- node service B -- DataModelA and B -- unique radis data store Do you know what is the best way to do this, or is there something already been built Many thanks, ty -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Stream video with node.js
So did you guys made it work? Could you share the final code? I am trying something similar here. Thx! On Tuesday, December 7, 2010 9:42:19 AM UTC-8, quantum wrote: Seems that you are incorrectly computing the content-length: var chunksize = (end-start)+1; If start is 0 and end is 1, in your case chunksize is 2, and it should be 1. That's why you're getting the 'loading' icon forever. Regards, Florin On Dec 7, 6:59 am, chrisharrington99 chrisharringto...@gmail.com wrote: I was able to get the video to play no problems in firefox by setting the connection header to close. Chrome is still a pain in my ass, but one step at a time... On Dec 6, 10:46 pm, chrisharrington99 chrisharringto...@gmail.com wrote: Deprecated or not, if I take the binary encoding out, the video doesn't play at all. On Dec 6, 4:21 pm, mscdex msc...@gmail.com wrote: On Dec 6, 1:25 pm, chrisharrington99 chrisharringto...@gmail.com wrote: response.end(file.slice(start, end), binary); The binary encoding is deprecated. Assuming 'file' here is instanceof Buffer, just passing in the slice should be enough since .write()/.end() can handle buffers and buffers contain binary data anyway. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] TypeError: DecipherFinal fail when crypted string longer than 15 characters
Hello everyone,
Recently I've upgraded my node to v0.8.8 and I encountered this strange
error (I'm not sure if it was present in previous node versions, though).
I have two functions for crypting and decrypting data in my application:
var cc_key = fs.readFileSync(path_to_key_file);
crypt = function(val){
var c = crypto.createCipher('aes256', cc_key.toString());
c.update(val, 'utf8');
return c.final('hex')
}
decrypt = function(val){
var c = crypto.createDecipher('aes256', cc_key.toString());
c.update(val, 'hex');
return c.final('utf8');
}
Both work just fine, unless I try to crypt and decrypt strings longer than
15 characters.
For example, doing:
var a = crypt(123456789012345);
console.log(decrypt(a))
works perfectly.
But doing:
var a = crypt(1234567890123456);
--- in here a = 694e42d3af6bd12b6fb6d165ca702e30 - so it's not empty and
seem to be ok ---
console.log(decrypt(a));
Throws: TypeError: DecipherFinal fail.
I'm not sure if I'm doing something wrong or there is a bug in crypto
module in node? I looked over the internet and it seems like a lot of
people have similar problems, but no-one knows the answer why is this
happening.
Paulina.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Beginner question about async function inside another function
What i want is to create a function to read files and return the files to
the caller.
This code is not working!
my func in coffeescript
fs = require('fs')
InitLoadTasks =-
a=[]
fs.readdir __dirname+ '/toRun', (err, files) -
if (err)
console.log(err)
a=files
initLoadTasks()
reads files from directory
how do i return the a array as a return value to InitLoadTasks?
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] TypeError: DecipherFinal fail when crypted string longer than 15 characters
On Tue, Sep 11, 2012 at 9:42 AM, Paulina Budzoń
paulina.bud...@gmail.com wrote:
Hello everyone,
Recently I've upgraded my node to v0.8.8 and I encountered this strange
error (I'm not sure if it was present in previous node versions, though).
I have two functions for crypting and decrypting data in my application:
var cc_key = fs.readFileSync(path_to_key_file);
crypt = function(val){
var c = crypto.createCipher('aes256', cc_key.toString());
c.update(val, 'utf8');
return c.final('hex')
}
decrypt = function(val){
var c = crypto.createDecipher('aes256', cc_key.toString());
c.update(val, 'hex');
return c.final('utf8');
}
Both work just fine, unless I try to crypt and decrypt strings longer than
15 characters.
For example, doing:
var a = crypt(123456789012345);
console.log(decrypt(a))
works perfectly.
But doing:
var a = crypt(1234567890123456);
--- in here a = 694e42d3af6bd12b6fb6d165ca702e30 - so it's not empty and
seem to be ok ---
console.log(decrypt(a));
Throws: TypeError: DecipherFinal fail.
I'm not sure if I'm doing something wrong or there is a bug in crypto module
in node? I looked over the internet and it seems like a lot of people have
similar problems, but no-one knows the answer why is this happening.
You need to concatenate the return values of update() and final(),
both when encrypting and decrypting.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] TypeError: DecipherFinal fail when crypted string longer than 15 characters
Wow, thanks a lot! I don't know how I could miss that...
Paulina.
W dniu wtorek, 11 września 2012 15:53:25 UTC+2 użytkownik Ben Noordhuis
napisał:
On Tue, Sep 11, 2012 at 9:42 AM, Paulina Budzoń
paulina...@gmail.com javascript: wrote:
Hello everyone,
Recently I've upgraded my node to v0.8.8 and I encountered this strange
error (I'm not sure if it was present in previous node versions,
though).
I have two functions for crypting and decrypting data in my application:
var cc_key = fs.readFileSync(path_to_key_file);
crypt = function(val){
var c = crypto.createCipher('aes256', cc_key.toString());
c.update(val, 'utf8');
return c.final('hex')
}
decrypt = function(val){
var c = crypto.createDecipher('aes256', cc_key.toString());
c.update(val, 'hex');
return c.final('utf8');
}
Both work just fine, unless I try to crypt and decrypt strings longer
than
15 characters.
For example, doing:
var a = crypt(123456789012345);
console.log(decrypt(a))
works perfectly.
But doing:
var a = crypt(1234567890123456);
--- in here a = 694e42d3af6bd12b6fb6d165ca702e30 - so it's not empty
and
seem to be ok ---
console.log(decrypt(a));
Throws: TypeError: DecipherFinal fail.
I'm not sure if I'm doing something wrong or there is a bug in crypto
module
in node? I looked over the internet and it seems like a lot of people
have
similar problems, but no-one knows the answer why is this happening.
You need to concatenate the return values of update() and final(),
both when encrypting and decrypting.
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups nodejs group.
To post to this group, send email to nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Beginner question about async function inside another function
If you're only doing it on startup, you could also use the synchronous version of readdir. On Sep 11, 2012 7:27 AM, Mark Volkmann r.mark.volkm...@gmail.com wrote: -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Totally failing on profiling my application
Hello, I'm desperately trying to profile my application, like I used to do with other languages where I could output some file I could pass to kcachegrind which would show me when and where the runtime executed my code. I'm running Ubuntu or Debian VM, whatever I've tried several methods: - Using dtrace on SmartOS: OK I can run dtrace, but I'm absolutely lost on SmartOS and I need many bricks like Redis and MongoDB I'm not sure how to install properly (I've compiled everything, which was a pita). Plus I'm not a sysadmin, which makes me waste ages each time I need to configure anything. Not forgetting the most recent provided zone (node-1.3.3) includes node v0.6.8. Dafuq ? - Using node --prof seemed very promising: simple, everything is embedded, cool :) I can generate a v8.log, OK. But then when I run deps/v8/tools/linux-tick-processor on it, I get no output, just an exit code 126. No idea what it means, I couldn't find information about this :( - Using valgrind I can output a callgrind file I can then use with kcachegrind. It's cool and I get real values, I can practically see the call chain, but I can't see my real function names. Instead I get some hexadecimal names, v8:: and node:: internals. That makes it quite useless for me :( - nodetime is great, but I'd really like a tool that doesn't rely on external service. Even if I finally stick with this solution, I need to have an alternative. Does someone know where error 126 comes from in linux-tick-processor ? Does what I'm looking for only exist: a profiler that would output stack and durations with the actual function names ? And easy to use on Linux x] Thanks a lot for all the information you can provide! I really want to get through that this time ;) -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Version 0.8.9 (Stable)
2012.09.11, Version 0.8.9 (Stable) * v8: upgrade to 3.11.10.22 * GYP: upgrade to r1477 * npm: Upgrade to 1.1.61 * npm: Don't create world-writable files (isaacs) * windows: fix single-accept mode for shared server sockets (Bert Belder) * windows: fix uninitialized memory access in uv_update_time() (Bert Belder) * windows: don't throw when a signal handler is attached (Bert Belder) * unix: fix memory leak in udp (Ben Noordhuis) * unix: map errno ESPIPE (Ben Noordhuis) * unix, windows: fix memory corruption in fs-poll.c (Ben Noordhuis) * sunos: fix os.cpus() on x86_64 (Ben Noordhuis) * child process: fix processes with IPC channel don't emit 'close' (Bert Belder) * build: add a --dest-os option to force a gyp flavor (Nathan Rajlich) * build: set `process.platform` to sunos on SunOS (Nathan Rajlich) * build: fix `make -j` fails after `make clean` (Bearice Ren) * build: fix openssl configuration for arm builds (Nathan Rajlich) * tls: support unix domain socket/named pipe in tls.connect (Shigeki Ohtsu) * https: make https.get() accept a URL (koichik) * http: respect HTTP/1.0 TE header (Ben Noordhuis) * crypto, tls: Domainify setSNICallback, pbkdf2, randomBytes (Ben Noordhuis) * stream.pipe: Don't call destroy() unless it's a function (isaacs) Source Code: http://nodejs.org/dist/v0.8.9/node-v0.8.9.tar.gz Macintosh Installer (Universal): http://nodejs.org/dist/v0.8.9/node-v0.8.9.pkg Windows Installer: http://nodejs.org/dist/v0.8.9/node-v0.8.9-x86.msi Windows x64 Installer: http://nodejs.org/dist/v0.8.9/x64/node-v0.8.9-x64.msi Windows x64 Files: http://nodejs.org/dist/v0.8.9/x64/ Linux 32-bit Binary: http://nodejs.org/dist/v0.8.9/node-v0.8.9-linux-x86.tar.gz Linux 64-bit Binary: http://nodejs.org/dist/v0.8.9/node-v0.8.9-linux-x64.tar.gz Solaris 32-bit Binary: http://nodejs.org/dist/v0.8.9/node-v0.8.9-sunos-x86.tar.gz Solaris 64-bit Binary: http://nodejs.org/dist/v0.8.9/node-v0.8.9-sunos-x64.tar.gz Other release files: http://nodejs.org/dist/v0.8.9/ Website: http://nodejs.org/docs/v0.8.9/ Documentation: http://nodejs.org/docs/v0.8.9/api/ Shasums: ``` 68aa7341807fb114f334151b7a1c8859e96b83d4 node-v0.8.9-darwin-x64.tar.gz 9e4a9422c1fd71750e9c46235d58aedaac3ba002 node-v0.8.9-darwin-x86.tar.gz 6236f781632555abf69d77f4bdfeb1e4e83779f3 node-v0.8.9-linux-x64.tar.gz 7f46084541d4909f44cfef2bb95f1e4f7435629e node-v0.8.9-linux-x86.tar.gz 33b0fe68f63519f3c8e6dc4d2aa51c96f62d2a56 node-v0.8.9-sunos-x64.tar.gz e05863cb3a7d4add340ad434228f57da04a03b3d node-v0.8.9-sunos-x86.tar.gz 104f325d5289c51c6eb6a0634691dcdb39abb1db node-v0.8.9-x86.msi 1dd2cf48fb9b1f3e11e6e6750084ad4b2a2b0a85 node-v0.8.9.pkg 2d3234adceedc2dc87284af88609ede6ecd71734 node-v0.8.9.tar.gz 2997e2075cd04cf693453ce5664fa37615faa9a7 node.exe d2834bd8ed3569b7880211dfe31a4f21cd475ab8 node.exp 41eac45ae350324de321a85787897bd8aa6b371c node.lib ab144b23b2594521d27a95fb36b0904d48a2 node.pdb f29db0a61a7bb32a7198ab059eca25b1283b9d6d x64/node-v0.8.9-x64.msi 2a7e69cef1bf7bc88109e007406e6feeaaa007b2 x64/node.exe 0423cd6602684c24e65358b9caa51740af67677b x64/node.exp 92155062a70100bfb5cf1389dd93e8851e7f3d0b x64/node.lib cbbee351b84d7da0a91f56d6bbf6805e7b85cc8f x64/node.pdb ``` -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] https.request error within chroot jailed node process
I'm getting the following error when calling https.request in my node script: nodejs: ../src/node_crypto.cc:752: void node::crypto::Connection::ClearError(): Assertion `handle_-Get(String::New(error))-BooleanValue() == false' failed. The node process is running inside a chroot on Ubuntu. I built the chroot using jailtool and as far as I can tell node should have all the necessary dependencies available to it. The way I checked was to run apt-rdepends nodejs and made sure that all the libs were inside the jail. The jail also has access to /dev/null and /dev/random. Besides https everything else seems to be running fine. I can make http calls no problem and the rest of my code runs without error. Running the same script outside the jail works. What am I missing? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: https.request error within chroot jailed node process
Oh I forgot to mention I'm running Node v0.8.8 on Ubuntu 12.04.1 in case that helps. On Tuesday, September 11, 2012 12:47:29 PM UTC-7, kuhnza wrote: I'm getting the following error when calling https.request in my node script: nodejs: ../src/node_crypto.cc:752: void node::crypto::Connection::ClearError(): Assertion `handle_-Get(String::New(error))-BooleanValue() == false' failed. The node process is running inside a chroot on Ubuntu. I built the chroot using jailtool and as far as I can tell node should have all the necessary dependencies available to it. The way I checked was to run apt-rdepends nodejs and made sure that all the libs were inside the jail. The jail also has access to /dev/null and /dev/random. Besides https everything else seems to be running fine. I can make http calls no problem and the rest of my code runs without error. Running the same script outside the jail works. What am I missing? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: https.request error within chroot jailed node process
Check to make sure that all of ssl's libs and all of it's certs are available inside the chroot too. I'm pretty sure they are loaded from /etc/ssl/certs/, so if that's not accessible from the chroot the request will likely fail. I seem to recall hitting this a while back, but it's been a while so I may be wrong. Dav -- Dav Glass davgl...@gmail.com blog.davglass.com + Windows: n. - The most successful computer virus, ever. + + A computer without a Microsoft operating system is like a dog without bricks tied to its head + + A Microsoft Certified Systems Engineer is to computing what a McDonalds Certified Food Specialist is to fine cuisine + On Tue, Sep 11, 2012 at 2:51 PM, kuhnza david.s.k...@gmail.com wrote: Oh I forgot to mention I'm running Node v0.8.8 on Ubuntu 12.04.1 in case that helps. On Tuesday, September 11, 2012 12:47:29 PM UTC-7, kuhnza wrote: I'm getting the following error when calling https.request in my node script: nodejs: ../src/node_crypto.cc:752: void node::crypto::Connection::ClearError(): Assertion `handle_-Get(String::New(error))-BooleanValue() == false' failed. The node process is running inside a chroot on Ubuntu. I built the chroot using jailtool and as far as I can tell node should have all the necessary dependencies available to it. The way I checked was to run apt-rdepends nodejs and made sure that all the libs were inside the jail. The jail also has access to /dev/null and /dev/random. Besides https everything else seems to be running fine. I can make http calls no problem and the rest of my code runs without error. Running the same script outside the jail works. What am I missing? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: https.request error within chroot jailed node process
Thanks Dav, the certs were missing from the chroot environment so I've copied them in now. Unfortunately I'm still getting the error though. Pretty sure all the required libs are there. I ran apt-rdepends on openssl and nodejs to be sure all those deps made it in there. Dave On Tuesday, September 11, 2012 1:25:11 PM UTC-7, Dav Glass wrote: Check to make sure that all of ssl's libs and all of it's certs are available inside the chroot too. I'm pretty sure they are loaded from /etc/ssl/certs/, so if that's not accessible from the chroot the request will likely fail. I seem to recall hitting this a while back, but it's been a while so I may be wrong. Dav -- Dav Glass davg...@gmail.com javascript: blog.davglass.com + Windows: n. - The most successful computer virus, ever. + + A computer without a Microsoft operating system is like a dog without bricks tied to its head + + A Microsoft Certified Systems Engineer is to computing what a McDonalds Certified Food Specialist is to fine cuisine + On Tue, Sep 11, 2012 at 2:51 PM, kuhnza david@gmail.com javascript: wrote: Oh I forgot to mention I'm running Node v0.8.8 on Ubuntu 12.04.1 in case that helps. On Tuesday, September 11, 2012 12:47:29 PM UTC-7, kuhnza wrote: I'm getting the following error when calling https.request in my node script: nodejs: ../src/node_crypto.cc:752: void node::crypto::Connection::ClearError(): Assertion `handle_-Get(String::New(error))-BooleanValue() == false' failed. The node process is running inside a chroot on Ubuntu. I built the chroot using jailtool and as far as I can tell node should have all the necessary dependencies available to it. The way I checked was to run apt-rdepends nodejs and made sure that all the libs were inside the jail. The jail also has access to /dev/null and /dev/random. Besides https everything else seems to be running fine. I can make http calls no problem and the rest of my code runs without error. Running the same script outside the jail works. What am I missing? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nod...@googlegroups.comjavascript: To unsubscribe from this group, send email to nodejs+un...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Another memory usage question / heapdump
We have a large application that continues to grow in memory usage as the day goes on (we restart it each day). I would like to not have to do that. We have been optimizing the crap out of the JS code and continue to do so and memory seems to be under control (or at least understood) in JS land. We have been using Ben's `heapdump` ( https://github.com/bnoordhuis/node-heapdump) module to take snapshots in production and analyze them offline. Right now one of our servers is sitting at 1.1 GB (RSS) and I just took a heap snapshot and the dump size is 75 MB.. I don't understand where this extra memory is coming from (Buffers?, we do a lot of requests, a bad addon module?). Not sure how to better debug this as the V8 tools don't seem to be helping. Any help appreciated. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Another memory usage question / heapdump
On Linuxy platforms, you can log and analyze native allocations with GCC's mtrace, which I've exposed to node here: https://github.com/Jimbly/node-mtrace Unfortunately, with any C++ allocations (which includes Buffers), they're all attributed to a single call site, operator::new, so your mileage may vary. If it's a rogue addon which is doing it's own memory allocations, it may help, or you may get lucky and something will jump out at you as suspicious. On Tuesday, September 11, 2012 1:51:40 PM UTC-7, wavded wrote: We have a large application that continues to grow in memory usage as the day goes on (we restart it each day). I would like to not have to do that. We have been optimizing the crap out of the JS code and continue to do so and memory seems to be under control (or at least understood) in JS land. We have been using Ben's `heapdump` ( https://github.com/bnoordhuis/node-heapdump) module to take snapshots in production and analyze them offline. Right now one of our servers is sitting at 1.1 GB (RSS) and I just took a heap snapshot and the dump size is 75 MB.. I don't understand where this extra memory is coming from (Buffers?, we do a lot of requests, a bad addon module?). Not sure how to better debug this as the V8 tools don't seem to be helping. Any help appreciated. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Stepped down from Nodejitsu as Chief Evangelist several months ago
Sad to see you go. Best of luck in the future. Cheers, Adam On Mon, Sep 10, 2012 at 5:41 PM, Luke Arduini lucasardu...@gmail.comwrote: Thanks for all you've done for the node community. Still my favorite pull request I've ever made: https://github.com/Marak/ohh/pull/4 On Sep 9, 11:05 pm, Marak Squires marak.squi...@gmail.com wrote: I wanted to make it clear to everyone here that I stepped down from any major roles at Nodejitsu several months ago to pursue other interests. I'm not sure why an announcement was not been made by Nodejitsu, so this is it now. - Marak -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- Better a little with righteousness than much gain with injustice. Proverbs 16:8 -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Giving up on node.js / Flatiron / hook.io
Sad to hear. It sounds like you won't be able to (or maybe don't want to, understandable), but will you be able to make any of your work toward 0.9 or its integration with Flatiron available anywhere? Were you planning to give ownership of the npm hook.io package, google group or github repo to anyone? I'll be forking, though it'd be nice if you planned to shut it all down to possibly hand these over (esp the github Issues). Either way, best of luck in the future. Cheers, Adam On Tuesday, September 11, 2012 8:56:37 AM UTC-7, Marak Squires wrote: Internet Friends - I'm sure it will come as a pleasant surprise for most of you to hear I'm leaving node.js for good. I'll also be stepping down from any involvement with Flatiron and completely shutting down hook.io In all honesty, I don't think there is much of a loss here for anyone. The Flatiron framework is pretty much pointless and I'd advise against using it. I started to add some really good reflection features, but since my access has now been removed from Flatiron, I'll no longer be able to advance or maintain any of these features. The same advice goes for hook.io. hook.io was a great idea, but it's been systematically made obsolete by Nodejitsu in favor of a closed source priority solution. I'd love to be able to share this with you, but it's closed source, so thats that. I was rebuilding hook.io to use Flatiron, but without the ability to work on Flatiron anymore, it's all moot. It's really sad to wind all this down, but I don't have a choice in the matter. I've been fired from Nodejitsu and no longer have the resources or git commit access to move any of this stuff forward. Anyway, thanks for all the good and bad times and goodbye. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: Why node + chrome rules the world...
In my opinion, there *still* aren't any web apps around, hahaha :) When I think about an app, it's gotta look and feel just like a desktop thing. Yeah, my project is real small right now, but I'm about to put something up that's pretty mindblowing. It's a kind of realtime, distributed community programming thing. I want it to be a combination of stackoverflow + github on steroids. You'll be able to dynamically update the Javascript that runs the site. Working code can now be deployed from my local console text editor to the remote clients in a small fraction of a second. It's all pretty hairy at the moment, but I should be able to smooth things out real nice in the next few days. I'm really investigating the possibility of an entirely new paradigm of programming... I must just go nuts in the process, though :P!! On Monday, September 10, 2012 4:47:43 AM UTC-4, Daniel Sousa wrote: eyeOS used to be great on the 1.x versions, but in 2009 the eyOS Team abandoned the 1.x series and started developing eyeOS 2.0 almost secretly and since then eyeOS has been more a commercial software than an open source project. Currently their website doesn't even mention there's an open source project. Lucid 2.0 was supposed to be developed on node.js, but there was basically just one person around it and he hasn't worked on it for a long time. These desktops were a great idea 5 years ago when there weren't any web apps and the word cloud wasn't even used, now these small projects would have a hard time competing with Google Docs et al. On Fri, Sep 7, 2012 at 3:43 PM, Dennis Kane dka...@gmail.comjavascript: wrote: Well, the necessary technology didn't really exist years ago. I rely very heavily on node/socket.io/websockets for the server side and Chrome's constantly developing API in the client. Trying to implement my current site with older JS engines and HTTP servers along with AJAX would be next to impossible. So I'm pretty excited about what I'm doing... the GUI is pretty intuitive and the websocket connection is lightening quick! On Friday, September 7, 2012 9:35:53 AM UTC-4, Karl Tiedt wrote: Yeah, Lucid started years ago now, and it was very active, not sure what happened with it, but it was pretty amazing at what it did for its time.. If nothing else, it may be good for some ideas, I didnt realize it has fell by the wayside :/ -Karl Tiedt -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nod...@googlegroups.comjavascript: To unsubscribe from this group, send email to nodejs+un...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Giving up on node.js / Flatiron / hook.io
Seconded. On Tuesday, 11 September 2012 14:17:29 UTC-7, Adam Crabtree wrote: Sad to hear. It sounds like you won't be able to (or maybe don't want to, understandable), but will you be able to make any of your work toward 0.9 or its integration with Flatiron available anywhere? Were you planning to give ownership of the npm hook.io package, google group or github repo to anyone? I'll be forking, though it'd be nice if you planned to shut it all down to possibly hand these over (esp the github Issues). Either way, best of luck in the future. Cheers, Adam On Tuesday, September 11, 2012 8:56:37 AM UTC-7, Marak Squires wrote: Internet Friends - I'm sure it will come as a pleasant surprise for most of you to hear I'm leaving node.js for good. I'll also be stepping down from any involvement with Flatiron and completely shutting down hook.io In all honesty, I don't think there is much of a loss here for anyone. The Flatiron framework is pretty much pointless and I'd advise against using it. I started to add some really good reflection features, but since my access has now been removed from Flatiron, I'll no longer be able to advance or maintain any of these features. The same advice goes for hook.io. hook.io was a great idea, but it's been systematically made obsolete by Nodejitsu in favor of a closed source priority solution. I'd love to be able to share this with you, but it's closed source, so thats that. I was rebuilding hook.io to use Flatiron, but without the ability to work on Flatiron anymore, it's all moot. It's really sad to wind all this down, but I don't have a choice in the matter. I've been fired from Nodejitsu and no longer have the resources or git commit access to move any of this stuff forward. Anyway, thanks for all the good and bad times and goodbye. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Re: errors when using node-gyp to build
One example is: /path/to/node /path/to/node-gyp.js --proxy=http://proxyhost.domain.com:8000 clean configure build I had to look at the source of node-gyp.js -Frank On Monday, April 23, 2012 5:28:25 PM UTC-5, Nathan Rajlich wrote: If you're behing a corporate proxy, then will have to set the PROXY environment variable, or set the --proxy switch to your the address of your proxy server. On Mon, Apr 23, 2012 at 2:13 PM, Ryan Cole ry...@rycole.com javascript: wrote: According to the node-gyp read me file, node-gyp will download required files. It looks to me like that download is failing for you. Ryan On Monday, April 23, 2012 12:45:22 PM UTC-5, SteveCronin wrote: Can someone help me figure out what is going on with this invocation of node-gyp? Where do I go for more information? node-gyp@0.4.1 /usr/local/lib/node_modules/**node-gyp hsd-test-iMac-1073:XYZApp admin$ node --version v0.6.15 hsd-test-iMac-1073:XYZApp admin$ which node /usr/local/bin/node hsd-test-iMac-1073:XYZApp admin$ sudo node-gyp -v configure build Password: info it worked if it ends with ok verb command 'configure' [] verb `which` succeeded for `python` '/usr/bin/python' verb no --target version specified, falling back to host node version 'v0.6.15' verb command 'install' [ 'v0.6.15' ] verb input version string 'v0.6.15' verb installing legacy version? true verb installing version '0.6.15' verb --ensure was passed, so won't reinstall if already installed verb version not already installed, continuing with install '0.6.15' verb created: '/Users/admin/.node-gyp/0.6.**15' info downloading: http://nodejs.org/dist/v0.6.**15/node-v0.6.15.tar.gzhttp://nodejs.org/dist/v0.6.15/node-v0.6.15.tar.gz verb got an error, rolling back install verb command 'remove' [ '0.6.15' ] verb using node-gyp dir '/Users/admin/.node-gyp' verb removing development files for version '0.6.15' ERR! Error: connect ETIMEDOUT at errnoException (net.js:670:11) at Object.afterConnect [as oncomplete] (net.js:661:19) ERR! not ok hsd-test-iMac-1073:XYZApp admin$ -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nod...@googlegroups.comjavascript: To unsubscribe from this group, send email to nodejs+un...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: ANN: Proxy npm module
looks pretty neat! makes dynamic content scrapping very scalable as you dont now have to load up a new webkit instance the server and could just do the scraping on the client side. On Tuesday, 28 August 2012 23:30:26 UTC+8, Dean Mao wrote: Doh, forgot to mention the library name: https://github.com/deanmao/xtend and an example usage of it: https://github.com/deanmao/xtend-example fetch via npm: npm install xtendme Let me know what you guys think! On Tue, Aug 28, 2012 at 8:27 AM, Dean Mao dea...@gmail.com javascript:wrote: I blogged about this briefly today: http://www.deanmao.com/2012/08/28/modify-a-site-you-dont-own/ It's similar to nodejitsu's http-proxy module only that it's for proxying 3rd party sites. It's like cgiproxy, only written for node. I'm just looking to see what other people think of it. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Node.js - authentication - Django
Hello list. I'm new here. A totally newbie trying to learn. I have a web application for internal use and developed with Django and running over Apache. In the app the access to every section is avaliable only for authenticated users with permissions over the view (except for the login). For this I use the authentication module provided for Django. The basic usage used for me is something like: @decorator_to_check_permission def my_view(request .. Now I must to create a section with multiple data and a lot of references and a lot of ajax. The section is almost finished. Just need one more thing. The info in the page can be edited by multiple users. If an user edit some section the other user must to refresh the page (or only a section with ajax) to see the changes. Well, this is ugly. For that I want to use node.js, just for this section inside the page. Learn about Comet and programming this. Timers+Ajax or hidden Iframes aren't in my plans. Now my question. Are any way to check if the user is authenticated and if have the permissions to get responses from node.js? Can I use the same authentification from Django or I must to use another authentification module from node.js? When the connection is opened? As you can see, i'm a little loss with this. Maybe my question is stupid or not logical, but I don't know... the change isn't easy ...at least for me. Bye, Cheers P.D.: Sorry for my english. Is ugly and rough. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Giving up on node.js / Flatiron / hook.io
Sorry to hear all that. I understand why you'd give up on nodejitsu and any related projects but why r u giving up on node.js as well? On Tuesday, September 11, 2012 11:56:45 AM UTC-4, Marak Squires wrote: Internet Friends - I'm sure it will come as a pleasant surprise for most of you to hear I'm leaving node.js for good. I'll also be stepping down from any involvement with Flatiron and completely shutting down hook.io In all honesty, I don't think there is much of a loss here for anyone. The Flatiron framework is pretty much pointless and I'd advise against using it. I started to add some really good reflection features, but since my access has now been removed from Flatiron, I'll no longer be able to advance or maintain any of these features. The same advice goes for hook.io. hook.io was a great idea, but it's been systematically made obsolete by Nodejitsu in favor of a closed source priority solution. I'd love to be able to share this with you, but it's closed source, so thats that. I was rebuilding hook.io to use Flatiron, but without the ability to work on Flatiron anymore, it's all moot. It's really sad to wind all this down, but I don't have a choice in the matter. I've been fired from Nodejitsu and no longer have the resources or git commit access to move any of this stuff forward. Anyway, thanks for all the good and bad times and goodbye. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Totally failing on profiling my application
On Tue, Sep 11, 2012 at 6:39 PM, Nicolas Chambrier naho...@gmail.com wrote: Hello, I'm desperately trying to profile my application, like I used to do with other languages where I could output some file I could pass to kcachegrind which would show me when and where the runtime executed my code. I'm running Ubuntu or Debian VM, whatever I've tried several methods: Using dtrace on SmartOS: OK I can run dtrace, but I'm absolutely lost on SmartOS and I need many bricks like Redis and MongoDB I'm not sure how to install properly (I've compiled everything, which was a pita). Plus I'm not a sysadmin, which makes me waste ages each time I need to configure anything. Not forgetting the most recent provided zone (node-1.3.3) includes node v0.6.8. Dafuq ? Using node --prof seemed very promising: simple, everything is embedded, cool :) I can generate a v8.log, OK. But then when I run deps/v8/tools/linux-tick-processor on it, I get no output, just an exit code 126. No idea what it means, I couldn't find information about this :( Using valgrind I can output a callgrind file I can then use with kcachegrind. It's cool and I get real values, I can practically see the call chain, but I can't see my real function names. Instead I get some hexadecimal names, v8:: and node:: internals. That makes it quite useless for me :( nodetime is great, but I'd really like a tool that doesn't rely on external service. Even if I finally stick with this solution, I need to have an alternative. Does someone know where error 126 comes from in linux-tick-processor ? Does what I'm looking for only exist: a profiler that would output stack and durations with the actual function names ? And easy to use on Linux x] Thanks a lot for all the information you can provide! I really want to get through that this time ;) Fedor has a callgrind script here[1]. Can you `npm install profiler` and check if nprof parses your v8.log file? If not, can you open a node-profiler issue? [1] https://github.com/indutny/callgrind.js -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Totally failing on profiling my application
In the same boat with nodetime. Recently stumbled across this project: https://github.com/baryshev/look Its basically a local nodetime client. I haven't used it quite yet, but it looks promising. On Tue, Sep 11, 2012 at 5:41 PM, Ben Noordhuis i...@bnoordhuis.nl wrote: On Tue, Sep 11, 2012 at 6:39 PM, Nicolas Chambrier naho...@gmail.com wrote: Hello, I'm desperately trying to profile my application, like I used to do with other languages where I could output some file I could pass to kcachegrind which would show me when and where the runtime executed my code. I'm running Ubuntu or Debian VM, whatever I've tried several methods: Using dtrace on SmartOS: OK I can run dtrace, but I'm absolutely lost on SmartOS and I need many bricks like Redis and MongoDB I'm not sure how to install properly (I've compiled everything, which was a pita). Plus I'm not a sysadmin, which makes me waste ages each time I need to configure anything. Not forgetting the most recent provided zone (node-1.3.3) includes node v0.6.8. Dafuq ? Using node --prof seemed very promising: simple, everything is embedded, cool :) I can generate a v8.log, OK. But then when I run deps/v8/tools/linux-tick-processor on it, I get no output, just an exit code 126. No idea what it means, I couldn't find information about this :( Using valgrind I can output a callgrind file I can then use with kcachegrind. It's cool and I get real values, I can practically see the call chain, but I can't see my real function names. Instead I get some hexadecimal names, v8:: and node:: internals. That makes it quite useless for me :( nodetime is great, but I'd really like a tool that doesn't rely on external service. Even if I finally stick with this solution, I need to have an alternative. Does someone know where error 126 comes from in linux-tick-processor ? Does what I'm looking for only exist: a profiler that would output stack and durations with the actual function names ? And easy to use on Linux x] Thanks a lot for all the information you can provide! I really want to get through that this time ;) Fedor has a callgrind script here[1]. Can you `npm install profiler` and check if nprof parses your v8.log file? If not, can you open a node-profiler issue? [1] https://github.com/indutny/callgrind.js -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] https.request error within chroot jailed node process
On Tue, Sep 11, 2012 at 9:47 PM, kuhnza david.s.k...@gmail.com wrote: I'm getting the following error when calling https.request in my node script: nodejs: ../src/node_crypto.cc:752: void node::crypto::Connection::ClearError(): Assertion `handle_-Get(String::New(error))-BooleanValue() == false' failed. The node process is running inside a chroot on Ubuntu. I built the chroot using jailtool and as far as I can tell node should have all the necessary dependencies available to it. The way I checked was to run apt-rdepends nodejs and made sure that all the libs were inside the jail. The jail also has access to /dev/null and /dev/random. Besides https everything else seems to be running fine. I can make http calls no problem and the rest of my code runs without error. Running the same script outside the jail works. What am I missing? Is your node binary installed from a repo? What happens if you compile from (upstream) source? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Memory leak, growing RSS and debugging
Nico did you have any luck in your debugging adventures? My symptoms seems to very closely match yours. Was going to try mtrace. On Monday, March 19, 2012 11:52:34 AM UTC-5, Nico Kaiser wrote: Thanks Ilya, I'll have a second look at node-mtrace. I tried this (as I did read the list ;-)), but it did not help much, and I hoped someone could identify a specific class of problems with my description (RSS grows, heap stays ok)... Nico Am Montag, 19. März 2012 16:06:38 UTC+1 schrieb Ilya Dmitrichenko: On 19 March 2012 14:09, Nico Kaiser ni...@kaiser.me javascript: wrote: How can I debug this behavior? I tried node-inspector, but v8-profiler only works with Node 0.4. Running node-gc every few seconds smoothes the memory curve, but does not help anything. If you did read the list, you would come across the same issue being discussed in this post: https://groups.google.com/d/msg/nodejs/Aq9BId5Tff8/7G3JxaIVd2YJ https://github.com/Jimbly/node-mtrace I observed that process.memoryUsage().heapTotal stays at an acceptable level (about 150 MB), only rss grows until the process gets killed. Does this tell anything, e.g. Buffer leak? (I know the WebSocket modules use lots of small buffers, but they should get freed, shouldn't they?). Do you have any hint where I can look for leaks? Thanks, Nico -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nod...@googlegroups.comjavascript: To unsubscribe from this group, send email to nodejs+un...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Another memory usage question / heapdump
Thanks Jimb, I will take a look at this. Very much a growing RSS problem but V8 heap staying reasonable. I am on Linux. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Giving up on node.js / Flatiron / hook.io
I'm going to miss your presence in the node community. You helped me get into node.js. Thank you for your contributions and I hope you find something enjoyable to work on next! Ben On Tuesday, September 11, 2012 9:56:45 AM UTC-6, Marak Squires wrote: Internet Friends - I'm sure it will come as a pleasant surprise for most of you to hear I'm leaving node.js for good. I'll also be stepping down from any involvement with Flatiron and completely shutting down hook.io In all honesty, I don't think there is much of a loss here for anyone. The Flatiron framework is pretty much pointless and I'd advise against using it. I started to add some really good reflection features, but since my access has now been removed from Flatiron, I'll no longer be able to advance or maintain any of these features. The same advice goes for hook.io. hook.io was a great idea, but it's been systematically made obsolete by Nodejitsu in favor of a closed source priority solution. I'd love to be able to share this with you, but it's closed source, so thats that. I was rebuilding hook.io to use Flatiron, but without the ability to work on Flatiron anymore, it's all moot. It's really sad to wind all this down, but I don't have a choice in the matter. I've been fired from Nodejitsu and no longer have the resources or git commit access to move any of this stuff forward. Anyway, thanks for all the good and bad times and goodbye. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Giving up on node.js / Flatiron / hook.io
You aren't punishing anyone but your fans if you give up now Marak. You don't need write access, this is open source. If you build it, they will come. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
[nodejs] Re: Giving up on node.js / Flatiron / hook.io
A pleasant surprise? I obviously know nothing about the nodejitsu firing, but your tutorials and IRC help were invaluable in getting me up on node and our start-up off the ground. For that you have my sincere thanks and we'll certainly miss your presence. -Brandon On Tuesday, September 11, 2012 11:56:45 AM UTC-4, Marak Squires wrote: Internet Friends - I'm sure it will come as a pleasant surprise for most of you to hear I'm leaving node.js for good. I'll also be stepping down from any involvement with Flatiron and completely shutting down hook.io In all honesty, I don't think there is much of a loss here for anyone. The Flatiron framework is pretty much pointless and I'd advise against using it. I started to add some really good reflection features, but since my access has now been removed from Flatiron, I'll no longer be able to advance or maintain any of these features. The same advice goes for hook.io. hook.io was a great idea, but it's been systematically made obsolete by Nodejitsu in favor of a closed source priority solution. I'd love to be able to share this with you, but it's closed source, so thats that. I was rebuilding hook.io to use Flatiron, but without the ability to work on Flatiron anymore, it's all moot. It's really sad to wind all this down, but I don't have a choice in the matter. I've been fired from Nodejitsu and no longer have the resources or git commit access to move any of this stuff forward. Anyway, thanks for all the good and bad times and goodbye. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Giving up on node.js / Flatiron / hook.io
Hey, I would do that, but I simply don't have the resources. I have no means to eat right now, let alone maintain open-source projects. I have no idea what I'll be doing next. No one is going to pay for the development of these tools, and I'm not going to ask anyone to. I'd go homeless ( again ) and continue to write open-source all day, but I just don't see the point in it anymore. I don't have the money or energy to continue. Starting over again for no real reason and with no budget is too daunting. I can't see a reason why I would want to endure any of this again. On Tue, Sep 11, 2012 at 9:12 PM, secoif sec...@gmail.com wrote: You aren't punishing anyone but your fans if you give up now Marak. You don't need write access, this is open source. If you build it, they will come. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
Re: [nodejs] Giving up on node.js / Flatiron / hook.io
http://www.reddit.com/r/Meditation/ Srirangan | +91 9711 477 595 | About http://srirangan.net/about GitHub https://github.com/Srirangan LinkedInhttp://www.linkedin.com/in/srirangan Twitter http://twitter.com/srirangan | Review19 http://review19.com Collaborate Track Decisions On Wed, Sep 12, 2012 at 10:27 AM, Marak Squires marak.squi...@gmail.comwrote: Hey, I would do that, but I simply don't have the resources. I have no means to eat right now, let alone maintain open-source projects. I have no idea what I'll be doing next. No one is going to pay for the development of these tools, and I'm not going to ask anyone to. I'd go homeless ( again ) and continue to write open-source all day, but I just don't see the point in it anymore. I don't have the money or energy to continue. Starting over again for no real reason and with no budget is too daunting. I can't see a reason why I would want to endure any of this again. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups nodejs group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
