The OHRRPGCE (RPG Construction Engine) is a tool for making your own retro 2D RPG games, in a style similar to RPGs like the older Final Fantasy games for the NES, SNES, or GBA. It includes, as an example game, Fenrir-Lunaris's pixel-art masterpiece 'Vikings of Midgard'. Feb 05, 2018 The game is supported on the following Macs. To check your Mac model and when it was released, select About This Mac from the Apple menu on your menu bar. All 21’5” iMacs since late 2013; All 27” iMacs since mid 2012 with a 1GB graphics card or better; All 13” MacBook Pros since late 2016. Furthermore, we recommend to use the PKG installer for Mac OS X because it includes the GAMS Studio and it integrates GAMS into Mac OS X, e.g. It is possible to open the GAMS Studio via the Launchpad. Two installation procedures are available for GAMS on Mac OS X. Feb 07, 2021 From the machines used to test that game, pick the one that resembles your Mac the most. Use the results from that machine as a comparison point. As an example, we’ve used the same 2013 13-inch MacBook Pro and 2016 13-inch MacBook Pro for every one of our Mac Performance Reviews. This is how they run some of the most popular Mac games right now.
Draft of Intro, Machine Description, and CPU Operations: | Tuesday, February 4 at 8am (start of class) |
Draft of Memory Operations: | |
Final report with all measurements plus code: | Thursday, March 12 at 8am (start of class) |
In building an operating system, it is important to be able todetermine the performance characteristics of underlying hardwarecomponents (CPU, RAM, disk, network, etc.), and to understand howtheir performance influences or constrains operating system services.Likewise, in building an application, one should understand theperformance of the underlying hardware and operating system, and howthey relate to the user's subjective sense of that application's'responsiveness'. While some of the relevant quantities can be foundin specs and documentation, many must be determined experimentally.While some values may be used to predict others, the relations betweenlower-level and higher-level performance are often subtle andnon-obvious.
In this project, you will create, justify, and apply a set ofexperiments to a system to characterize and understand itsperformance. In addition, you may explore the relations between someof these quantities. In doing so, you will study how to usebenchmarks to usefully characterize a complex system. You should alsogain an intuitive feel for the relative speeds of different basicoperations, which is invaluable in identifying performance bottlenecks.
You have complete choice over the operation system and hardwareplatform for your measurements. You can use your laptop that you arecomfortable with, an operating system running in a virtual machinemonitor, a smartphone, a game system, or even a supercomputer.
You may work either alone or in 2–3 person groups. Groupsdo the same project as individuals. All members receive the samegrade. Note that working in groups may or may not make the projecteasier, depending on how the group interactions work out. Ifcollaboration issues arise, contact your instructor as soon aspossible: flexibility in dealing with such issues decreases as thedeadline approaches.
This project has two parts. First, you will implement and performa series of experiments. Second, you will write a report documentingthe methodology and results of your experiments. When you finish, youwill submit your report as well as the code used to perform yourexperiments.
Your report will have a number of sections including anintroduction, a machine description, and descriptions and discussionsof your experiments.
sysctl
on BSD, /proc
on Linux, System Profiler on Mac OS X, the cpuid
x86 instruction), or online. Gathering this informationshould not require much work, but in explaining and analyzing yourresults you will find these numbers useful. You should report atleast the following quantities:Do not underestimate the time it takes to describe your methodologyand results.
Evaluate for the TCP protocol. For each quantity, compare both remote and loopback interfaces. Comparing the remote and loopback results, what can you deduce about baseline network performance and the overhead of OS software? For both round trip time and bandwidth, how close to ideal hardware performance do you achieve? What are reasons why the TCP performance does not match ideal hardware performance (e.g., what are the pertinent overheads)? In describing your methodology for the remote case, either provide a machine description for the second machine (as above), or use two identical machines.
During the quarter you will have read a number of papers describing various system measurements, particularly in the second half of the quarter. You may find those papers on the reading list useful as references.
In addition, other papers you may find useful for help with systemmeasurement are:
You may read these papers, or other references, for strategies onperforming measurements, but you may not examine code to copy orreplicate the implementation of a measurement. For example, readingthe lmbench paper is fine, but downloading and looking at the lmbenchcode violates the intent of the project.
Finally, it goes almost without saying that you must implement allof your measurements. You may not download a tool to perform themeasurements for you.
We will grade your project on the relative accuracy of yourmeasurement results (disk reads performing faster than the buffercache are a bad sign) as well as the quality of your report in termsof methodology description (can we understand what you did and why?),discussion of results (answering specific questions, discussingunexpected behavior), and the writing (lazy writing will hurt your grade).
In the past, a frequent issue we see with project reports is thatthey do not clearly explain the reasoning behind the estimates,methodology, results, etc. As a result, we do not fully understandwhat you did and why you did it that way. Be sure to explain yourreasoning as well.
As a first stage of the project, we would like you to submit anearly draft of the first part of the project. What should you coverin the draft? The first two parts of the report (Introduction and Machine Description), and the first set ofoperations (CPU, Scheduling, andOS Services). For this step only submit a draft of the report,not your code.
What percentage of the project grade does it form? It will onlybe worth 5% of your grade. Why so little? The idea with the initialdraft is that it is primarily for your own benefit: it will get youstarted on the project early, and it will give you a sense for howlong it will take you to complete the project by the end of thequarter (in the past, students have reported that it has taken them40-120 hours on the project). As a result, you should be able tobetter budget your time as the end of the quarter arrives. How roughcan the draft be? Your call — again, this is primarily for yourbenefit.
In the second stage of the project, extend your report draft withresults for the second set of operations (Memory). Please also hand in your gradedreport from the first stage for reference.
For the drafts, bring one hardcopy per group with you to class onthe deadline.
For the final project reports, submit them in pdf to me and the TA via email. Also submit your code to us via email as well, packaged either as a tar.gz or a zip file.