- Home Page
Categories
Archives
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- June 2011
- May 2011
- April 2011
- February 2011
- January 2011
- December 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- February 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- June 2006
- May 2006
- April 2006
- February 2006
- November 2005
- October 2005
- September 2005
- June 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
Daily Archives: February 10, 2006
PaperCut NG 6.1 released!
Wow, it’s been a very long time since my last post… I am alive!
We’ve been really busy over the past few months making PaperCut NG even better, and just released version 6.1. It adds a number of often requested features like LDAP, but some of the best improvements have been under the covers in the User Client, including:
- Much faster print notifications
- Much improved scalability when running thousands of clients simultaneously
- Reduced bandwidth usage
- More robust when the client can’t connect to the server upon startup
We had a client running the User Client on almost 2000 workstations simultaneously!! And this was putting considerable load on the PaperCut Application Server, so we had to rethink our approach. The result was a large re-write of the client and the code on the server that handle client connections. If you’re a software developer and you’ve ever ever had to do this type of optimization, you’ll know that it’s quite tricky. You’ll also know that the bottlenecks are often not where you thought they would be.
But the effort was worth it!
The client now consumes very little bandwidth (10% of the bandwidth it did previously), the print notifications are almost instantaneous, and the server handles thousands of simultaneous connections without breaking a sweat.
… anyway … back to work!