Week 4 CST 334

This week, I focused on understanding memory virtualization and its role in operating systems. I explored various techniques such as segmentation, paging, and swapping. Segmentation organizes memory into logical sections like code and data, which works well for modular programs, though it can lead to external fragmentation. Paging, on the other hand, divides memory into fixed-size pages, minimizing gaps but potentially causing internal fragmentation when pages are underutilized. I also learned about segmented paging, a hybrid approach that combines the benefits of both methods but adds complexity. Additionally, I studied swapping, where the system moves data between RAM and disk to handle memory shortages. However, excessive swapping can lead to thrashing, significantly degrading system performance. It was fascinating to see how these techniques work together to optimize memory management.

In the lab, I implemented a FIFO (First-In-First-Out) page replacement algorithm to study the relationship between cache size and performance. By running simulations with varying cache sizes, I analyzed how increasing cache size reduced the miss rate, but only up to a point of diminishing returns. I visualized the data using graphs, which helped me better understand how caching and memory management algorithms balance efficiency and resource constraints. This combination of theoretical learning and practical application gave me a deeper appreciation for the complexities of memory virtualization and the systems that make it possible.

 

Comments

Post a Comment

Popular posts from this blog

CST 462S - Learning Journal (service learning)

Working with the American Technology Initiative was really fun, informative, and rewarding. I spent most of my time on their volunteer portal, a prototype level app that makes volunteer reporting way easier. The codebase was almost release ready, so I got to dive in, explore its parts, and see how a familiar tech stack scales up for real users. Since the core features were already in place, I focused on user testing: hunting bugs, suggesting little tweaks, and polishing usability. Even though these were small changes, it felt great knowing they’d make a real difference for volunteers. If there’s one thing I’d change, it’d be the length of the service learning project. 25 hours (over eight weeks) barely gives you time to get comfortable with a new codebase. From my experience, you need at least forty hours just to learn the ropes and even more to add substantial features. I’d love to see future SL programs run at least 120 hours (about six months) so you can really dig in. The highlight...
Read more

CST 300 Week 7

Part 1: Arranging our ultimate research video project was a great experience for us as a team. The entire process was smooth, we all agreed with the concepts that were brought forth and maintained a steady vision during the planning phase. We collaborated mostly during our weekly zoom meetings. With different operating systems, we had to use various tools such as iMovie, powerpoint and Final Cut Pro (which is what I used). Looking back on it now though, what I would suggest is having timelines that allow us to finish the project at least a week early so that we can then look at it and try to improve it. However, our team has a strong bond so sharing each other’s ideas into our projects was easy for us. Part 2: I viewed Lera Boroditsky’s TED Talk “How Language Shapes the Way We Think.” The speaker discusses how much influence languages have on our thoughts and perceptions. She gives examples of different ways in which languages can shape reality, affecting even such basic phenomena as s...
Read more