Searcharxiv⌕ Search

arXiv subjects

Faraz Gurramkonda

Publications and source records attributed to Faraz Gurramkonda.

2 recordsLinked to original sources

Mining Unity VR Repositories for Refactoring Patterns and Technical Debt

Maintaining virtual reality (VR) applications poses challenges tied to real-time performance, hardware dependencies, and complex interactions. Yet little is known about how developers refactor these applications, which kinds of technical debt they address, or how well automated tools capture VR-specific changes. We mined 1,755 candidate refactoring commits from 176 open-source Unity VR repositories and manually examined a sample of 303 commits, of which 270 contained at least one refactoring. We also extended RefactoringMiner to create VRRefMiner, a tool that detects conventional refactorings in C# scripts used by Unity applications. Our analysis found both conventional and VR-specific refactorings. VR-specific changes addressed concerns such as interaction logic, performance, and Unity-specific artifacts. Code debt was the most prevalent category overall, while interaction debt and UI/UX debt were the main categories addressed by VR-specific refactorings. Across the repositories, VRRefMiner detected 15,549 operations spanning 68 refactoring types, with structural moves and extractions accounting for 31.0% of detections. It detected conventional refactorings in 216 of 246 commits labeled as general refactoring. In the 24 commits labeled as VR-specific, the tool could detect conventional changes but identified no VR-specific refactoring categories. These results point to a need for detection techniques that account for both source code and the Unity artifacts involved in VR maintenance.

cs.SE↗

Docker Containers vs. Virtual Machines: A Comparative Study of Architecture, Performance, Configuration, and Security

Modern application platforms must isolate workloads while preserving deployment speed, portability, resource efficiency, and security. Virtual machines (VMs) and Docker containers address this requirement at different abstraction layers: VMs virtualize hardware and run independent guest operating systems, whereas containers isolate processes while sharing the host kernel. This paper presents a comparative, literature-based analysis of the two approaches across architecture, configuration and lifecycle management, performance, scalability, and security. Published studies generally associate containers with shorter startup times, smaller images, higher workload density, and near-native execution for many workloads. These benefits depend on workload characteristics, storage and network drivers, resource controls, and experimental design. VMs introduce greater overhead but offer independent kernels, heterogeneous guest operating systems, and a stronger isolation boundary. The comparison therefore treats efficiency and isolation as a design trade-off rather than declaring one technology universally superior. A hybrid architecture, in which containers run inside hardened VMs, often provides a practical balance for cloud and multi-tenant systems.

cs.SE↗