We wanted to make sure that we "minimized our ripple" since our goal was/is not only to push out the new platform support but also to support / cleanup / coalesce all that we touch.Īs Martijn mentioned above, we are also heavily invested in a robust CI for tests and builds, and we wanted to make sure that we ran functional tests on all platform, combinations. We wanted to signal to the OpenJDK community that we were here to collaborate and help with the Java platform.Īs for the most challenging part: I think when we started working on the port, we realized that we would be touching shared code in the linux-aarch64 code base as well as the windows-x86-64 code base. Given our Windows developer base, it made sense to us to have the Windows port be our first big contribution to the OpenJDK ecosystem. Red Hat had already done a great job of porting OpenJDK to Linux on Arm64. Our first WoA offering for developers centered around the modern, cloud-based environment is the Surface Pro X device.Īrm64 has a rich ecosystem and with the introduction of Arm servers, it was clear that we needed to have a Java port to support our investment in " driving innovation with ARM server processors for use in our data centers". Kudos to Monica's leadership and the work of her team they managed this from start to finish and were simply excellent.īeckwith: Windows (10) enablement on Arm (WoA) is a big effort at Microsoft. It's the level of care and attention that makes me particularly proud of this group's efforts they set a high bar for this sort of work. Doing no harm to what was already there (Linux aarch64) was really important to us, but it did take a lot of engineering cycles to get the patches right and to do the thorough testing on both platforms. When you're adding support for a new port there's the brand new code to add, and then (IMO) the more complicated reworking of the shared code. Testing (functional, performance, and regressions of both).Splitting up the patches into easily digestible chunks by the OpenJDK community (four patch sets in this case).With regards to the challenges of the port, from my standpoint it was interesting to see the time and effort that the team spent on: ![]() Our Surface X Pro line runs on ARM hardware and in 2017 we announced our intent to trial ARM on our cloud infrastructure. Verburg: Microsoft has two areas of interest with regard to ARM. Why did you get started with ARM? Which was the most challenging problem to tackle? How did it go? What would you have done differently? InfoQ: This is the first big contribution from MS to OpenJDK. Prior to Microsoft, I worked as the performance architect for managed runtimes at Arm. I have mostly been working on the performance side of things working with optimizing the apps, the JVM, the GC heuristics, and making sure that the generated code sympathizes with the underlying hardware. I have worked with OpenJDK since Sun started the project/effort back in 2006. My day-to-day work involves improving OpenJDK’s Hotspot VM. Monica Beckwith: Hello, I am Monica and I am the lead of OpenJDK’s Windows on Arm64 project. ![]() There are some rumors that I'm the "Diabolical Developer", but since I'm a manager that can't be true -). Some of you may know me previously from my role as CEO of jClarity (who MSFT acquired last year) or as one of the Steering Committee members at AdoptOpenJDK or at Jakarta EE. Martijn Verburg: Hi all, I'm Martijn Verburg and I'm the principal SWE group manager for the Java Engineering Group at Microsoft. Can we start by asking you to introduce yourselves and describe your roles and day-to-day at Microsoft? InfoQ: Thank you for taking the time to answer some questions for our readers. Is it already possible to switch to a Surface Pro as your Java developing machine? Can we benefit from the performance of ARM processors on Azure? InfoQ reached out to her and Martijn Verburg, principal SWE group manager for the Java Engineering Group, to explore more what this means for the Java community. ![]() ![]() The porting effort was the first project led by Monica Beckwith since she joined Microsoft. Specifically, that means that one can develop and run Java code on Windows 10 ARM operating machines. Microsoft’s enthusiasm for ARM processors with its availability on notebooks and lately in cloud environments, has been taken one step further. This summer, Microsoft made its first big contribution to OpenJDK: the first phase of porting OpenJDK to Windows 10 ARM (AArch64).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |