Migrate, Modernize and Build Java Web Apps on Azure: This live workshop will cover methods to enhance Java application development workflow.
Modern Digital Website Security: Prepare to face any form of malicious web activity and enable your sites to optimally serve your customers.
Founder at Chronon
San Mateo , US
Joined Jul 2010
About
Prashant is the Oz behind Chronon. Inspired and frustrated by years of breakpoint guesswork in the current debuggers and fumbling with printin() statements and logging frameworks, Prashant set out to find a different way to debug programs. Chronon is the result of his efforts.
Stats
Reputation: | 313 |
Pageviews: | 46.1K |
Articles: | 1 |
Comments: | 42 |
Articles
Comments
Apr 04, 2012 · Jimmy Vu
Minor correction of a mistake on my part:
The answert to the first question should read:
further our mission of 'No more Non Reproducible Bugs'
not
further our mission of 'Non Reproducible Bugs'
Sorry I was too excited with all the stuff happening today :)
Apr 04, 2012 · James Sugrue
Minor correction of a mistake on my part:
The answert to the first question should read:
further our mission of 'No more Non Reproducible Bugs'
not
further our mission of 'Non Reproducible Bugs'
Sorry I was too excited with all the stuff happening today :)
Jul 19, 2011 · Prashant Deva
Jul 19, 2011 · Prashant Deva
Jul 19, 2011 · Prashant Deva
Jul 19, 2011 · Prashant Deva
Jul 18, 2011 · Prashant Deva
Jul 18, 2011 · Prashant Deva
Jul 18, 2011 · Prashant Deva
Jul 18, 2011 · James Sugrue
Conditional breakpoints are merely an evolution which do not solve the fundamental design issues with the breakpoint model, which is that programs are long running and bugs are not easily reproducible. If your program breaks after running for 4 hours, good luck trying to debug it using conditional breakpoints.
Also if you have used the expressions view in Eclipse, you know if the expressions results in a complex hierarchy of method calls, the expressions view wont evaluate it.
Jul 18, 2011 · James Sugrue
Conditional breakpoints are merely an evolution which do not solve the fundamental design issues with the breakpoint model, which is that programs are long running and bugs are not easily reproducible. If your program breaks after running for 4 hours, good luck trying to debug it using conditional breakpoints.
Also if you have used the expressions view in Eclipse, you know if the expressions results in a complex hierarchy of method calls, the expressions view wont evaluate it.
Jul 18, 2011 · James Sugrue
Conditional breakpoints are merely an evolution which do not solve the fundamental design issues with the breakpoint model, which is that programs are long running and bugs are not easily reproducible. If your program breaks after running for 4 hours, good luck trying to debug it using conditional breakpoints.
Also if you have used the expressions view in Eclipse, you know if the expressions results in a complex hierarchy of method calls, the expressions view wont evaluate it.
Jun 14, 2011 · Gerd Storm
Jun 14, 2011 · Gerd Storm
Jun 14, 2011 · James Sugrue
Jun 14, 2011 · James Sugrue
Jun 08, 2011 · Gerd Storm
This is exactly the kind of misconception I am talking about.
If your app uses extra memory then yes, there will be extra GC.
However, setting the -Xmx values does not *make* your app use extra memory, it only *allows* it to use the memory if it needs to.Jun 08, 2011 · Gerd Storm
This is exactly the kind of misconception I am talking about.
If your app uses extra memory then yes, there will be extra GC.
However, setting the -Xmx values does not *make* your app use extra memory, it only *allows* it to use the memory if it needs to.Jun 08, 2011 · James Sugrue
This is exactly the kind of misconception I am talking about.
If your app uses extra memory then yes, there will be extra GC.
However, setting the -Xmx values does not *make* your app use extra memory, it only *allows* it to use the memory if it needs to.Jun 08, 2011 · James Sugrue
This is exactly the kind of misconception I am talking about.
If your app uses extra memory then yes, there will be extra GC.
However, setting the -Xmx values does not *make* your app use extra memory, it only *allows* it to use the memory if it needs to.Jun 04, 2011 · Dev Stonez
May 17, 2011 · James Sugrue
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.
May 17, 2011 · James Sugrue
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.
May 17, 2011 · Gerd Storm
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.
May 17, 2011 · Gerd Storm
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.
May 17, 2011 · Gerd Storm
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.
May 17, 2011 · James Sugrue
2. In case of large heaps, 2gb and above, the extra overhead doesnt matter much. Also java objects can be created out of the heap size only.
3. The article constantly refers to the system having 24gb or 6gb or more of memory and thus a 64 bit system. Anyway that is not the point of this article. The article is not about how much memory you should allocate but the misconception that if you specify a max heap, that doesnt mean all the ram is immediately used by an application. It just means the application is allowed to use extra memory if needed.
May 16, 2011 · Gerd Storm
You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.
Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.
May 16, 2011 · Gerd Storm
You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.
Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.
May 16, 2011 · Gerd Storm
You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.
Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.
May 16, 2011 · James Sugrue
You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.
Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.
May 16, 2011 · James Sugrue
You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.
Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.
May 16, 2011 · James Sugrue
You are paranoid. At the bottom the 'article' clearly states that this is a blog post in my blog. Last I checked, I was allowed to write about my software in my own blog.
Javalobby has decided to run this as an article since the issue of misconceptions regarding java heap size arguments apply and benefit the larger Java community and the troubles we had with Chronon almost serve as a real life case study of the pain it is to work around these arguments and the misconceptions people run into when an actual product has a high value defined for the heap size arguments.
Mar 07, 2011 · James Sugrue
Mar 07, 2011 · James Sugrue
Mar 07, 2011 · James Sugrue
Jul 14, 2010 · Christopher Penkin
Jul 14, 2010 · Christopher Penkin
Jul 14, 2010 · Christopher Penkin
Jul 14, 2010 · James Sugrue
Jul 14, 2010 · James Sugrue
Jul 14, 2010 · James Sugrue