cache performance

Previously I had a serious performance issue on my website.
The reason is that I have a big menu with 130+ menu links.
Content access module was breaking the block caching, and the website page loading was 4 times slower. It was a real head banging until I found what causes that issue.

I've removed the content access module and wrote a custom code for block caching.

Right now I've added a Advanced forum on the same website with many features.
Unfortunately I have to use Forum Access module, because real forum is nothing without permissions.

I have a site setup were I am benchmarking boost with nginx vs nginx with microcaching and it shows that using microcaching produces a First Byte Time of around 0.984s while nginx+boost without microcaching produces 0.257s.

I know that microcaching should be producing better or similar numbers but in my case it's the appositive.

I like to get to the bottom of this odd issue.

P.S I am using perusio's d6 branch

We have a Pressflow 6 app with Cache Router routing to multiple memcache bins. The bins have plenty of memory allocated, but other than that are running with default options.

In local testing, I've found that some basic cache-setting fails because of object size. Examples:

Hey everyone,

Question for you on Drupal cache. Our new site, nhpr.org, is running on two servers to handle an increasing amount of traffic. The servers sync up their MySQL data instantly, so that if a user edits a node, the edit registers on both servers immediately. Problem is, Drupal's cache is getting in the way of this sync process, so if there's an edit made on the nodes the database data is indeed the same, but the site will display the old data on the second server, until I manually flush the cache.

Duration: 1 hour

Brief description: How do you create a site that can handle millions of page views per day without crumbling under the load? Caching won't solve all your site problems, but it has to be part of your strategy. In this session we'll cover Drupal's internal caching mechanisms, what Memcache can do for you, the types of scenarios that Varnish can cover, and the whys and wherefores of Edge Caching. We'll discuss the differences between building a static site that can handle thousands of page requests per second, and what it means to your performance when you start adding authenticated users and node edits.

I'm working on a unique problem right now with the relaunch of a high traffic site (2-5 million page views per day), and want to run an idea by the group. There is a specific singular landing page that will receive a significant amount of traffic from an external source, and each requested page would have a unique query parameter. Ex: /landing-page?uid=438474383487348?foo=bah.

I'm looking for a solution to a content publication issue and I think Views might be the answer, but I'm not sure how or if I could configure it to work. Any advice, ever for alternative methods, is appreciated. The situation is this: