A sparkline (or any graphic) is a matrix of points (pixels), that they in this case make proportional (resize to fit) the associated location (insertion point) in your document.
Part of what they're trying to patent, is sizing an inline graphic to the same height as your font.
This is why you have
a) The development environment on the dev's local PCs, where they can fuck about as much as they want,
b) The development SERVER, where you are willing to install stuff from time to time to get their committed code to run and get real testing,
c) The staging server, which is kept as close as possible to your production environment, and where code is tested in production-like circumstances,
d) The production server, surrounded with plenty of slow, painful deathtraps for developers.
We're still on 5, indeed. Work is currently ongoing to integrate our patches (in as far as necessary) into Drupal 6, and then upgrade site by site.
We've looked at the Boost module, too, about a year ago, and found then that it wasn't what we needed. Again, the dev guys know better than I why:-)
The cache interference issue was, as far as I can tell, to do with clear_cache calls or something of that ilk emptying the entire bin instead of just the keys it should. Don't know much details, but it got worked around by splitting the bins.
And, yes, our sites are running on a cluster of by now 8 webservers, against two separate MySQL databases. One DB could handle the load, but we left the most troublesome site behind when we installed a new one:-)
I agree that you can't do much cross-module optimizing of your queries, but I've got logs that show literally dozens of nearly-identical queries on a single cache table for a single pageview (not all of our sites already have all of our optimizations).
Something I suspect may be an issue when moving to InnoDB is that the entire database layout and usage scheme might not be very optimal for InnoDB's clustered indexes. I haven't looked at that yet, though, so I don't know how big the impact would be.
When I say 'large', I don't mean data volume - that's something that databases are built to handle pretty well. I'm talking about the amount of pageviews, which runs into the millions per month for all our sites combined.
I'm fully aware that Drupal already caches content - that very feature was the cause of quite some trouble: if you're gonna use caching tables, it's rather unwise to lock them for selects whenever you update them; which is at most every page request (that gets through the squid, of course), also true for the session table. This is why we've moved to memcache for caching, although that brought it's own challenges, especially for cache invalidations.
We've looked at the block cache, but I'm not entirely sure wether we're using it, or why not. The block cache, like all of Drupal's cache layer, still requires PHP execution, though - I wish we could more easily relegate logged in pages to Squid. Nature of the beast, I suppose.
We don't have shared content, every site has it's own codebase atm. We *are* considering moving to multisite,though, so our optimisations get implemented in all sites at once.
You may not agree with focus upon a single DB, and you're right that you cut your potential public, but you'd also be much improving your out-of-the-box performance, which would gain you more, imo. This is of course a matter of personal preference - personally I would prefer a better product to a larger userbase. I'm not familiar with the SQL rewriting facility, but it feels wrong to have to bother re-writing something that's already in the application, however convenient you make the process.
My DBA experience is the same any DBA would have seen: I found that the tables are mostly well-layed out and well-indexed, but the entire design of the application is so that you can't even gain any benefit from moving to row-locking InnoDB without modifications to the code.
Is it in any way conceivable to your narrow mind that both premises may be possible *at once* in a nation of 1 billion ? Same as the US is generally good to live in for most citizens, but the state still commits atrocities like gitmo at times ?
Yes, there's things in China that shouldn't be - and likely more and worse than in your and my parts of the world, but for the majority of the 1 billion people, life is reasonably good. They'll get there, eventually, and so will you.
Slashdot Mirror
Their southern neighbours, the Belgians, tend to have a distinct opinion on that. Not at all related to their living below sea level, though :-)
Planescape: Torment ?
A sparkline (or any graphic) is a matrix of points (pixels), that they in this case make proportional (resize to fit) the associated location (insertion point) in your document.
Part of what they're trying to patent, is sizing an inline graphic to the same height as your font.
I'm not trying to patent NTFS. I'm patenting using NTFS on my computer.
Can you run multiple independant instances of Girlfriend 2.0 with it ?
Because the NSA is out to collect intelligence, which means they have very little of it themselves.
So what you're saying is that this was the reboot halfway the upgrade process ?
Like you don't have any unusual fetishes.
This is why you have
a) The development environment on the dev's local PCs, where they can fuck about as much as they want,
b) The development SERVER, where you are willing to install stuff from time to time to get their committed code to run and get real testing,
c) The staging server, which is kept as close as possible to your production environment, and where code is tested in production-like circumstances,
d) The production server, surrounded with plenty of slow, painful deathtraps for developers.
> 'set it and forget it'
Which makes for an interesting walk if you come by there yourself afterwards.
Wormwood ? We're gonna get flooded by Absinthe when the endtimes come ? Damn, dude, count me in. How soon can we get there ?
Sounds to me like one of you guys is coding business-critical stuff, while the other one is doing websites for marketing.
eh. Girly boys are hot either way :-)
I like how you specify "life enriching".
Webcam and "magic" markers ? Have an eyepet: http://www.youtube.com/watch?v=aPENA1Bpm68
Shut up, voice in my head.
> At this point the coffin is made entirely of nails.
I guess it's being held together by sheer force of will, then, or possibly faith.
We're still on 5, indeed. Work is currently ongoing to integrate our patches (in as far as necessary) into Drupal 6, and then upgrade site by site.
:-)
:-)
We've looked at the Boost module, too, about a year ago, and found then that it wasn't what we needed. Again, the dev guys know better than I why
The cache interference issue was, as far as I can tell, to do with clear_cache calls or something of that ilk emptying the entire bin instead of just the keys it should. Don't know much details, but it got worked around by splitting the bins.
And, yes, our sites are running on a cluster of by now 8 webservers, against two separate MySQL databases. One DB could handle the load, but we left the most troublesome site behind when we installed a new one
I agree that you can't do much cross-module optimizing of your queries, but I've got logs that show literally dozens of nearly-identical queries on a single cache table for a single pageview (not all of our sites already have all of our optimizations).
Something I suspect may be an issue when moving to InnoDB is that the entire database layout and usage scheme might not be very optimal for InnoDB's clustered indexes. I haven't looked at that yet, though, so I don't know how big the impact would be.
When I say 'large', I don't mean data volume - that's something that databases are built to handle pretty well. I'm talking about the amount of pageviews, which runs into the millions per month for all our sites combined.
I'm fully aware that Drupal already caches content - that very feature was the cause of quite some trouble: if you're gonna use caching tables, it's rather unwise to lock them for selects whenever you update them; which is at most every page request (that gets through the squid, of course), also true for the session table. This is why we've moved to memcache for caching, although that brought it's own challenges, especially for cache invalidations.
We've looked at the block cache, but I'm not entirely sure wether we're using it, or why not. The block cache, like all of Drupal's cache layer, still requires PHP execution, though - I wish we could more easily relegate logged in pages to Squid. Nature of the beast, I suppose.
We don't have shared content, every site has it's own codebase atm. We *are* considering moving to multisite,though, so our optimisations get implemented in all sites at once.
You may not agree with focus upon a single DB, and you're right that you cut your potential public, but you'd also be much improving your out-of-the-box performance, which would gain you more, imo. This is of course a matter of personal preference - personally I would prefer a better product to a larger userbase. I'm not familiar with the SQL rewriting facility, but it feels wrong to have to bother re-writing something that's already in the application, however convenient you make the process.
My DBA experience is the same any DBA would have seen: I found that the tables are mostly well-layed out and well-indexed, but the entire design of the application is so that you can't even gain any benefit from moving to row-locking InnoDB without modifications to the code.
> Nothing in corporate America is illigeal or immoral; until caught that is.
There, fixed that for you.
Hmm... And here I was, thinking waterboarding was an american invention.
I was more thinking of Jesus Camp, but yeah.
You're quite right. "Knowing about it but not caring enough to bother doing something about it" is not the same as "being sanctioned".
Or beaten up, shot and/or murdered because you're gay. Or black. Or because the redneck over there just didn't like you.
Oh, wait, we were talking about China, sorry.
Is it in any way conceivable to your narrow mind that both premises may be possible *at once* in a nation of 1 billion ? Same as the US is generally good to live in for most citizens, but the state still commits atrocities like gitmo at times ?
Yes, there's things in China that shouldn't be - and likely more and worse than in your and my parts of the world, but for the majority of the 1 billion people, life is reasonably good. They'll get there, eventually, and so will you.