Well, now that support is available at http://developers.sun.com/services/expertassistance/ . It's resonably priced - well actually its dead cheap if you do any decent amount of Java development. And I wasn't even looking for that, it was highlighted somewhere or other and I clicked through. So Sun, well done. Somehow your marketing found me, and your offering is great value. Here's one more suggestion. Stick a link on the front page menu of Java pages where you have "Popular Downloads" etc - it would fit really well in that "Resources" section.

Well done, Sun, looking better than you have for a long time.]]> 2008-01-02T17:42:16Z 2005-12-30T10:37:19Z tag:weblogs.java.net,2005:/blog/jacksjpt/63.3865 2005-12-30T10:37:19Z

  //Note I am putting this code fragment in the public domain
  public static final Pattern TidyHTMLLineNotification = Pattern.compile("^line\\s+(\\d+)\\s+column\\s+(\\d+)\\s+\\-\\s+(.*)$");
  static HashMap TidyNoficationsToIgnore = new HashMap();
  static
  {
    TidyNoficationsToIgnore.put("newsletter013.shtml+Warning: discarding unexpected </p>", Boolean.TRUE); 
    TidyNoficationsToIgnore.put("Warning: trimming empty <p>", Boolean.TRUE); //always ignore
  }
  public static void validateHTML(File destinationfile)
    throws IOException, InterruptedException
  {
    //Stdout to tt.txt, stderr to t2.txt.
    //tt.txt contains fixed HTML if you want it.
    //t2.txt contains Tidy's warnings and errors
    String command = "Tidy -o tt.txt -f t2.txt " + destinationfile;
    Runtime.getRuntime().exec(command).waitFor();
    BufferedReader rdr = new BufferedReader(new FileReader("t2.txt"));
    String line;
    while( (line = rdr.readLine()) != null)
    {
      //Only interested in lines beginning with "line"
      if (line.startsWith("line "))
      {
        Matcher m = TidyHTMLLineNotification.matcher(line);
        if (m.matches())
        {
          String linenumstr = m.group(1);
          String colnum = m.group(2);
          String message = m.group(3);
          if ( (TidyNoficationsToIgnore.get(message) != Boolean.TRUE) &&
               (TidyNoficationsToIgnore.get(destinationfile.toString()+'+'+message) != Boolean.TRUE) )
          {
            //line number in destinationfile of problem. Read the file
            //and get that line and the line before
            int linenum = Integer.parseInt(linenumstr);
            BufferedReader rdr2 = new BufferedReader(new FileReader(destinationfile));
            String l2 = null, l1 = null;
            for (int i = 0; i < linenum; i++)
            {
              l1 = l2;
              l2 = rdr2.readLine();
            }
            rdr2.close();
            rdr.close();
            throw new IOException("HTML Validation Problem Identified by Tidy in file " + destinationfile + ": line " + 
		linenum + " / " + message + System.getProperty("line.separator") + l1 +System.getProperty("line.separator") + l2);
          }
        }
      }
    }
    rdr.close();
  }
}

If you have an interest, go ahead and start a site about it. It may or may not pay off, but you can't win if you don't try.

To make your reading experience more efficient, I have decided to put the summary points at the top of this and future articles. I guess that the summary points from this article would be:

• The greater the legitimate traffic to your site, the more you can make from your site.
• Make sure you have interesting focused information on your site.
• Keep adding interesting information to your site and notify your readership when you add content. The content is the most important part of your site, and is the real reason why legitimate traffic will continue to grow.
• When you first open the site, make a big splash by announcing your site to your community: post once wherever it is acceptable to do so.
• Promote your site. Look for publicity how you can, e.g. write articles for popular magazines. If you can figure out how to get one of your own website articles referred to around the web or at popular locations, this is often a good boost.
• Community websites tend draw more traffic (discussion groups and blogs), so consider adding support for one to your site.

There, you don't need to read the rest of this now. If you do, please note that I add a list of hyperlinks detailing this month's JavaPerformanceTuning.com newsletter contents at the end.

A couple of weeks after I opened my site, I already had more Java performance tips for the site, and I realized that if I just tagged them on to the tips page they would not even be noticed. At the same time, I had been reading up on websites and found out a few things. Primarily, there were two aspects to getting people to view a website. One was getting them to the site, the other was keeping them there. Or more specifically getting them to come back. All these sources of information were pointing out that "content is king". Of course content provision is only one type of service, there are other services like search engines, discussion sites, webmail providers, auction sites, blogsites and so on. The vast majority of sites are content provision, because they are the easiest to get running. They also have a big advantage for individuals: most niche subjects are not catered for by any commercial sites. That's because it is not worth their doing so unless the subject has enough people interested and enough capable writers to make the readership significant. In this niche area, you can thrive. And who knows, maybe you are at the begining of something about to take off!

I'd better take a step back and explain something: Why do I want people to come to my site at all? Well, initially, I was hoping that the more people that come to my site, the more likely it was that one of them would want to use my services (at the time consulting services). And ultimately, that hasn't changed - though the services I can provide have extended. But this is the crux, the most important point about making money from a website. The more people you have coming to the site, the more money you can make from it. Indeed, some ways of making money from your site only start to kick on when you have enough people already coming to your site. Note, that there are devious and unethical ways to get people to come to your site. I do not advocate any of these, and have never used any. I think that ultimately these techniques would backfire, and those extra users that are inappropriately directed to your site will not benefit you. So when I talk about getting people to come to your site, I'm talking about them coming legitimately, because your site provides something they are looking for.

For a site that provides content, the more interesting information you put on the site, the more likely it is that people looking for that information will come to your site. In my case I knew that people are interested in Java performance tuning. And I looked around the web for information about Java performance, but I knew that I already had way more content than anyone else, since I had summarized all the existing content as well as adding my own. And this thinking was validated by Google - within three weeks of opening the site, Google had me listed in the top twenty results for searches on "Java performance". A few weeks later I was in the top ten.

So aspect 1, content, was taken care of me. What about getting people to come back? Well, I had new tips to list, and I wanted to point out they were new, and not have them lost amongst the thousand already listed. So it was an easy step to decide on having a monthly newsletter listing the new tips. Hardly a new idea, but important nevertheless. And by December 2000, two months after opening the site, I had a fabulous total of 48 subscribers to send my first newsletter to. I had extracted the tips from five new articles (and some older ones), a couple written by me. In fact, I had started writing articles at O'Reilly's instigation. They asked me for two to help publicize my book, one to come out a couple of weeks before book launch, and the second a couple of weeks after. I enjoyed writing, so I had carried on and also submitted an article to JavaWorld ("Optimizing Queries on Maps"), and they had published that together with Brian Goetz's article "Optimizing I/O Performance" in the same week. Looking at the sad spectacle that was JavaWorld until recently, that just shows you how much they have changed. They paid money for articles in those days. Good money. And such was the site popularity and the advertising return, that they could afford to publish two interesting articles in the same week. In fact, they did that most weeks. I hope the re-launched Javaworld is eventually just as successful .

The JavaWorld article taught me an important lesson. The articles I had published at O'Reilly's sites had increased hits to JavaPerformanceTuning.com a little. On the day my JavaWorld article was published, my site hits tripled! The day before I had about 150 hits, publication day saw 420 hits. It was my first introduction to the world of referral spikes. Nowadays, sites pray to be "slashdotted", as it is now called (after the effect of having a popular discussion occur on slashdot.org about some page on your site). Back then, I suddenly found out that other sites make a big difference to the volume of traffic hitting your site. Well Doh! Okay, I kind of knew that in an abstract way, but I didn't really expect the "spike and tail". You get the spike when the other site publishes, then it tails off after a couple of days, but you still end up with higher daily traffic than before the spike.

My strategy since that starting month hasn't really changed. Maintain good content. Add content on a regular basis. I've added a number of different columns to our newsletter, so much so that we are now more a magazine than anything else. In fact all the columns I have now were identified pretty early on, in the first few months. But it has taken years to organize having them all available on a regular basis.

There are aspects that I haven't yet implemented which make for heavier traffic. For a content provision site, the main one is adding discussion groups, a secondary one is having a useful search engine. Blogsites (like the one carrying this article) tend to also get decent amounts of traffic boost, but require much higher levels of input - once a month blogging doesn't really attract traffic unless there are lots of bloggers each contributing once a month.

I blog on java.net and artima. It doesn't generate that much traffic for me, even when I write a very useful well referred blog (like this one on Java Case Studies). Mostly, I don't really set out to write my blogs for their promotion effects, because they are not worth it. Not cost effective for me. You see, an article by me published on my website actually brings in more readers than writing on any of these forums. I know this to be the case because I have the hard numbers, the references from the java.net & artima sites, and the number of extra readers I got each time I added an extra article to the newsletter output. On the other hand, I know of other sites who are desperate for a mention here because it makes a significant difference to their traffic.

In my opinion, where it is most worth writing other than your own site is at magazines that pay for your output. I'm not even talking about the direct payment reward. Between us, my colleague Kirk Pepperdine and I have written for many of the locations where a Java interest article could be published. The better they pay, the better the quality of response coming through to the JavaPerformanceTuning site. I have a theory about why this should be. It's quite simple really. They can afford to pay because they are making money from their articles, because of the quality or volume of their readership. And you get the reflected glow of that readership. Simple rule: if you are going to write somewhere else, write for the place that pays you the most. You'll probably get a double benefit from that.

But let's get back to site promotion. The primary way of promoting your site is valuable content. Search engines reference you, people reference you, sites reference you, all because you have some useful and relevant information. This leads to slow but steady growth in traffic to the site, as long as you keep the content interesting. Secondary ways include writing articles. One of the most useful ways is to get a discussion going about your content. Aim to publish something particularly newsworthy a couple of times a year or, very occasionally, something controversial. My biggest spike was when I published a list of performance tips from JavaOne 2003. Funny, because I publish almost the same volume and same quality of performance tips every month. But that time, the reference got propagated around the web a lot more, had a few discussions about it, and consequently got more references than any other article I've written. I got the usual spike and tail, just bigger than before.

Newbie Java sites have a tendency to post the opening to their site on every Java interest site that they are able to. And any big items also tend to get posted wherever they can. Announcers of new products, and new versions of products do the same. And it works (but do post in appropriate forums, not just anywhere). For the initial boost, post once everywhere. I didn't do this because I didn't think of it at the time, but I have since followed the stats for few sites that did. As long as the content is relevant and interesting, this is a great way to get a flying start. Just remember that you do get diminishing returns, i.e. it is not worth doing too often. (How do I follow other site stats? Well some publish them, which is very helpful. Some publish full historical stats, some publish recent stats only which requires regular visits to maintain your knowledge. Some will give you the information if you ask. Some have their stats listed by one of the automatic stat summary programs, and you can access those summaries if you know where to look).

Ultimately, keep an eye on your site-visit growth curve. As long as the growth is more or less steady, just keep adding interesting content. If growth starts flagging, is there a good reason? (9/11 saw some sites take a dip in their growth curve for a few months). If not, you might need to do something to get it going again.

Next time, in part 3 "Site Design & Technology", I'll talk about the technical site aspects. Meanwhile, you might want to check our most recent newsletter (April 2004):

• We list all the latest Java performance related news and articles
  • "I got more responses for that pattern article than I have for almost anything else on this site"
• Double Dispatch.
  • What is double dispatch? This old technique doesn't get the exposure it deserves. Here, Kirk Pepperdine explains how it operates and where it is used, with examples. Read on ...
• The roundup of performance discussions over the last month. Kirk covers maintainability vs. performance, SQL tuning, Value objects, messaging and more
  • "But still, I see the technique being used quite often and the excuse offered is that it is there for performance. The lesson learned is: measure, don't guess."
• Javva The Hutt rambles through performance past, present and future. Javva does some tuning
  • "Slowly, with a configuration change here, a code change there, I started to make headway."
• This month's interview with Gavin King, Hibernate founder
  • "We don't see Hibernate as an "inexpensive" alternative ... Rather, we think people use Hibernate because it is a better fit to their requirements, is more stable, and better supported."
• Question of the Month asks how to profile applets
  • "even better is to have the applet start up with almost no resources and minimal class file content"
• All the latest Java performance tips extracted in concise form
  • "Availability is binary: on or off. Usability includes responsiveness and performance consistency. High availability does not equal high usability!"
• A new cartoon by "profiler". This month: clustering to reduce overheads

"What features do you have that your competitors don't?" I asked.

"We don't have any competitors" was the reply.

Admittedly, these two guys were young, despite their impressive sounding titles of "senior something" and "something else seniorish". But even so you would think they would know better. So in the hope that they or their spiritual bretheren are reading this blog, let me give you a few words of advice.

The statement "We don't have any competitors" does NOT tell your potential customers that you have a fantastic new product which no-one has ever thought of. It tells potential customers that your product must be one they don't need. After all, if you have no competitors, the market must be so small that no-one else thinks it worthwhile to build a competing product.

So listen guys, get to know at least a couple of your biggest competitors. And find some weakness in their product which yours addresses. Then when I ask my question, you'll have an answer that doesn't suggest to me that you are working for a company that is going down the tubes because it can't train it's reps decently. Because "We don't have any competitors" is synonymous with "we have nothing of interest here".

I didn't intend to run a website to make money. Back in late 2000, the dot boom had already turned to dot bust, people were already being layed off left and right, and it was clear that websites, B2B, B2C, ... were no longer the "in thing". If you hadn't raised money for a web venture, then you weren't going to, at least not for a few years when the VC [venture capital] doors might start opening a hair's breadth. I knew all about every aspect of these things, because I was an independent consultant who was also loosely attached to a couple of startups. I say "was attached", but "had been attached" would be more accurate. My skills hadn't changed any, but the climate had and every startup I knew was busy closing their doors. If you weren't in, then you weren't going to be in, no matter how "attached" you were. If you were in, there was a good chance that you wouldn't be very shortly. In fact every startup I knew of went rapidly back to the "twinkle in the eye" stage, with their principals looking for work.

So, all in all, not an auspicious time to start a web venture. But then, I didn't think I was starting a web venture. You see, my first book was just about to be published (Java Performance Tuning, O'Reilly). And like every author, I was sure that my book was brilliant, that every Java developer in the world would go rushing out to buy a copy, that they'd all be clamouring for my attention. And naturally, I needed a place where people could contact me. So I started a website, using the name of my book as the domain name, "JavaPerformanceTuning.com". A few people pointed out to me that this was a pretty long-winded name. But then I wasn't thinking in terms of people typing in the domain, this wasn't ebay. It was just a point of contact. I figured most people would get my name from the book, do a search for "Jack Shirazi" and click through from the search; or go to the publisher's website, and find a hyperlink that just clicked through to the site.

Up front, I knew there had to be something on the site more than just "this is me and this is what I do". I mean it's all very well to get the odd click-through to your site, but how many people are interested in your bio? And after they've read the bio, what more is there? No, I realized up front that this site was going to be a support site for my book, so I started putting together resource pages and stuff. I also realized that this would be a good place to list anything that interested me about Java performance, since if it interested me, it might well interest other people (ah, ego). So I pulled out any tips from interesting pages online, and by the time I opened the site I already had a thousand Java performance tips. I guess I had more time on my hands back then.

My favorite opening tip was one from an Intel document on optimizing software running on Intel chips, which included a section on Java. My tip said

• "I've only included this here because it's so (unintentionally) funny. Their only tip seems to be "use the JNI to write it in native code", which is not even a good tip."

Not long after I put that tip up, the referred to Intel document was deleted from Intel's website, which made me feel quite good. Of course it could have been a coincidence, but I like to think that some of the half a dozen people or so visiting the site in the first month were influenced enough to make Intel make the change. I like to think that, but even the vainest part of me recognizes that coincidence is a far more likely reason. More recently, Intel has published interesting and informative articles on Java, so like everyone else they've come to take it much more seriously. So kudos to them, always good to see a company reform its ways and get away from the dark side.

So the site was opened (October 23 2000), and I registered on a dozen or so search engines. My first hits came in almost immediately! Whoah, I was excited. Suddenly I could see fame and fortune rearing ahead of me. On the first day alone I had 25 hits. I calculated that if only one in 10 was interested in my services, I'd be rolling in it. Yes!

Boy oh boy, how naive can you be! Well I'm not sure about you, but clearly I can be pretty naive. One in ten. I crack up now just thinking about the idea that one in ten clicks might get me anything. Bear in mind I was not even thinking unique site visits, or even page views, at the time. I was actually calculating ahead my affluent future based on hits to the site, and a ten percent response rate! If all this is another world to you, and you can't see the reality dislocation, it's like expecting one in ten viewers of a TV advert for double glazed windows to call in to the advertised telephone number. And that includes the viewers who taped the advert and wind through at fast forward, and the viewers who popped out to get a drink, etc. If that happened, you could think in terms of a world where the biggest one hundred companies are all TV stations. Not going to happen. If a million people watch an annoying TV program (not advert, a program), you might get ten of them calling in to complain. If it is a nice program, you might get one calling in to praise it. The web is much more interactive, but one in ten responding? Not going to happen.

And what about those first 25 hits? Number one was the Altavista spider. Number two the Lycos spider. In fact all 25 were either one of these two spiders, or me looking at the site, or someone from O'Reilly who was checking it because I had asked them to put a link from their page of my book to my site. Day 2 saw a friend hit the site, day 3 saw the Googlebot. If I had bothered to analyze my meager ration of httpd log entries, I would have quickly realized that it was going to be a long slog before I had even ten people hitting the site.

Next time, in part 2 "Keep 'Em Coming", I'll talk about the two important aspects in getting people to come to your site. Meanwhile, you might want to check our latest newsletter (March 2004)

• We list all the latest Java performance related news and articles
  • "performance news continues to show just how hot Java performance tools are this year"
• The Commando Pattern
  • "The Commando Pattern provides specialized access to methods and variables to enable optimal performance in critical and non-critical sections of code."
• Kirk's roundup of performance discussions over the last month covers memory tuning, caching, session state, obscure flags, 1.5 enhanced loop and more
  • "good news on the enhanced loop syntax found in the JDK 1.5. There is no performance penalty for using the new syntax."
• Javva The Hutt rambles through performance past, present and future. Javva continues his diary and writes a memory monitor with some interesting side effects
  • "I've written a little memory monitoring class ... It also has some extra features which ... well, lets just say they are proprietary."
• Question of the Month: Why is a long primary key bad for performance?
  • "Good primary keys are essential to good database design."
• All the latest Java performance tips extracted in concise form
  • "The practical difference between a 95 percent cache hit rate and a 96 percent cache hit rate is 20 percent!"
• A new cartoon by "profiler". This month: reducing unnecessary communication overheads

• We list all the latest Java performance related news and articles
  • "any system that doesn't have low overhead monitoring capabilities on it's basic statistics is really not a mature system."
• Learning From Code: Fast Random Access.
  • "How many interfaces are there in the JDK that have no fields and no methods? What are these interfaces used for? Read on ..."
• The roundup of performance discussions over the last month. Kirk covers object relational mapping tools, the performance difference in iterators and enumerations, different GC algorithms, and more
  • "Certainly the NIO package has received some attention [in 1.5] as preliminary results have caused at least one jaw to drop. "
• Javva The Hutt rambles through performance past, present and future. Javva finds he's become a news star
  • "more than one internal website now featured a picture of me in one of those "Wanted, Dead or Alive" posters."
• This month's interview with Lax Sakalkale, Senior Product Manager of the Optimizeit performance solutions
  • "we have Lax giving us almost a manual of how to proceed to ensure you achieve good performance in your project, especially noting which pitfalls to avoid"
• Question of the Month asks how to choose which feature to use
  • "Write beautiful code; then profile that beautiful code and make little bits of it uglier but faster"
• All the lastest Java performance tips extracted in concise form
  • "Trust hard numbers from a performance tool more than a document claiming that only one SQL statement will be issued per user transaction"
• A new cartoon by "profiler". This month: reading in parallel

For me, the most interesting of items in the news was the server side discussion which floated the idea of pushing NIO support into J2EE. What a wealth of information. NIO select support costing 5% to 30% overhead compared to the blocked multi-thread model came as a real surprise to me. Though maybe it shouldn't since a blocked thread mostly only takes up non-CPU resources, while the Select multiplexing model explicitly exchanges those per-thread resources with active socket set management. I think the 5% mark is probably the more accurate though, because excellent as a product Jetty is, I've noticed several inefficiencies that it has, along with many webservers (see this old study if you want to understand how even minor effects can dramatically affect the scalability of webservers). In fact we use Jetty in our performance training classes, and profiling the socket transfers is quite instructive for our students. And that's not to say I wouldn't use it in production. On the contrary, if it fitted the functional requirements I'd certainly test its performance against the other possible solutions.

Other than that, you might also want to check out the fail fast article if you haven't noticed the ConcurrentModificationException possibilities inherent in using the List iterators, and our other columns are also quite interesting:

• We list all the latest Java performance related news and articles
  • "more proof that Java is going from strength to strength. Now that's a nice way to start 2004."
• Learning From Code: Fast Fail Iterators.
  • "What is a mysterious field called modCount doing in the List Iterator classes? How can we efficiently handle iterating over collections when another thread may be updating the collection at the same time? Read on ..."
• The roundup of performance discussions over the last month. Kirk covers session beans, timing distributed calls, garbage collection and more
  • "Yet more proof that the engineers at Sun fully realized that optimizers such as HotSpot are sensitive to coding style and with that realization, built HotSpot with good coding practices in mind "
• Javva The Hutt rambles through performance past, present and future. This month Javva has a "wow!" moment, and gets visted by Agent Smith
  • "Agent Smith visited us. You know, the one from the Matrix? Black shades, wire coil hanging behind his ear, precise speech patterns, shady motives."
• This month's interview with Bela Ban, lead for JBossCache
  • "what we want to do here is to use our transactional replicated cache to actually keep the cached entity beans in memory. This will greatly improve performance"
• Question of the Month asks about profiling J2EE applications
  • "J2EE applications are often of such complexity that there can be bottlenecks which are difficult to identify without jumping through hoops"
• All the lastest Java performance tips extracted in concise form
  • "Some small optimizations (like turning logging down) can yield huge gains"
• A new cartoon by "profiler". This month: Lazy Initialization

• We list all the latest Java performance related news and articles
  • "we've only been building up steam on the Java steamroller. The real ride is only just starting. Whoopee, it's full steam ahead!"
• The roundup of performance discussions over the last month. Kirk covers when to use PL/SQL, a "semi-deployed" system, time syncing distributed systems, and more
  • "whenever a thread drifts at Java Gaming, it's always for the better"
• Javva The Hutt is on holiday
  • "A pittance would be a fortune compared to what we get."
• This month's interview with Jayson Falkner, Mr. JSP
  • "Here are the best tricks I use: #1 Database Connection Pooling; #2 Don't read flat files from the hard disk; #3 Server-Side Caching; ..."
• Question of the Month asks about the -Xprof HotSpot profiler
  • "is -Xprof useful? Yes, after all you are getting some profiling information for almost nothing"
• Our new cartoon section by "profiler". This month: Speeding up the hardware

Okay, I had nine responses to last month's question about about the appropriateness of these announcements. Seven were positive, indicating that I should carry on announcing the availability of the JavaPerformanceTuning.com newsletter, one was neutral, and one negativish. In fact, the main feedback outside "carry on" was that I should put some additional content along with the announcement. Which seems fair enough. So I'll have a go at giving you some opinions in addition to the announcement in future. Meanwhile, here are some stats.

To put those nine active responses into context, the November announcement was read about 800 times up to now, and generated about the same number of reads on to the JavaPerformanceTuning.com newsletter. The November newsletter pages were read about 10 000 times (back copies were read another 7 000 times during December). And for those of you who are interested, our most popular single newsletter page to date was the June 2003 page detailing new performance tips extracted from JavaOne 2003, which has now been read 23 000 times.

JavaPerformanceTuning.com gets hits from all round the world. The last time I looked, we had about a third of our traffic coming from the USA, a third from Europe, and a third from everywhere else. So can you guess which day over the year was the quietest in terms of traffic? ... Take a moment, think about it and try not to peek ahead ... okay, well the answer is the first of January. I guess that's the most popular day worldwide for a hangover. And for the two hundred or so sober web denizens who looked up pages on JavaPerformanceTuning.com last Jan 1st, I'll be joining you tomorrow as I did last year, since I don't get the day off either.

• We list all the latest Java performance related news and articles
  • "Free profiler number 19 and number 20 are listed in the tools this month"
• The roundup of performance discussions over the last month
  • "For a posting to collect so many responses that are all tightly focused on the original question, you know that you?ve run into a topic where people?s experiences are universal."
• Javva The Hutt rambles through performance past, present and future
  • "this is I.T. If you do something long enough to become an expert, you can be sure that your skillset is going down the tubes"
• This month's interview is with Bruce Tate, Mr. Antipattern.
  • "We ditched EJB, in favor of a simple POJO solution"
• Question of the Month: Dealing with OutOfMemoryError
  • "Reducing application memory may be simple, you may just be allowing some collections to be too big, for example using many large buffers. Or it can be complex, requiring you to reimplement some classes, or even redesign the application."
• All the lastest Java performance tips extracted in concise form
  • "100 new tips extracted from Bruce Tate"

If you missed the October issue, the contents of that issue are here

Someone (I don't know who) told someone (I know who) who told me that they think my announcements of my newsletters are not appropriate for a blog. They suggested that this was plain advertising. I actually agree that this announcement is advertising. The question is, do you find it useful? I am advertising relevant Java content on a Java interest website. The content is accessible for free, not even registration is required. Personally, I'm delighted when someone points out relevant material from their blog, and I couldn't care less if they are a member of the organization that provides the material. But I'll happily go with the flow.