I was of course assured that my choice didn't mean I'd get it, but it was an interesting hallway poll for the day. I suspect the answers were being pulled together as input for this week's Linux Foundation meetings happening this week in Austin Tx... lots of people in town.
The mind races.
So back to the Linux Weather Forecast. Whew. What to choose, what to choose.
- http://www.linux-foundation.org/en/Linux_Weather_Forecast written up by Jonathan Corbet of lwn.net fame.
- A new completely fair scheduler - the promise of an updated scheduler is intriguing for performance teams. Course, on a practical level, the thoughts of rather extensive regression testing keeps popping up in my mind. Watching the progress of that effort is reassuring though, so this will be cool in the next revs of the distros.
- Kernel markers - cool technology which will make it easier for tools to hook into the kernel, which of course a performance team is always interested in. We need to make it absolutely seamless and safe for a customer, on a production system, as a protected but definitely non-root user, to gather system metric information.
- Memory use profiling- now this will be really nice - way too many times we're asked about memory usage of an application - which is particularly dependent on other things happening in the operating system.
- Real-time enhancements - continued integration of the real-time work happening in parallel in the community. This is proving particularly helpful in the HPC cluster space as work continues to improve the deterministic behavior of the operating system.
- Memory fragmentation avoidance - another longer-term project which positions the kernel for far more aggressive memory management and control of varying page sizes.
- And numerous other choices... better filesystems in ext4 and btrfs, better virtualization and container support, better energy management, improvements in glibc, etc etc
So what I asked for was for the kernel and Linux community to continue strengthening the ability to help customers easily understand and improve the performance of their applications and the system. Out of the box. Across all of the components. No special adds, rpms, or kernels on their installed system.
The nice part is the Linux programmers I work with are all committed to this. So the work continues - fit, finish, and polish - and continue working with the longer term changes which are being developed.
3 comments:
there is no option which would satisfy everybody
Marti - the point isn't to use one item to satisfy everyone - but what one thing would *you* want in the kernel? A lot of people have lists and are working on them, as Bill's blog suggests, but imagination fuels innovation. What comes next? The session I am in now focuses on the desire to have laptops run on battery power for as long as possible - which enables disconnected operation. That's good for a lot of us. Feel free to point out what one thing *you* would like.
Hi Bill,
I'm afraid that this comment is related to your post. Actually I have one question and searching a Linux guru to answer that.
How can I get page scan rate on Linux? While this comes in vmstat o/p on Solaris, I didn't find it in linux. Any way?
Basically, I am developing a method for memory forecasting on linux systems. I thing page scan rate is best metric for memory workload. What do you think?
Thanks,
Neeraj
Post a Comment