A
A. Omar Portillo-Dominguez
Researcher at University College Dublin
Publications - 22
Citations - 142
A. Omar Portillo-Dominguez is an academic researcher from University College Dublin. The author has contributed to research in topics: Garbage collection & Workload. The author has an hindex of 8, co-authored 20 publications receiving 121 citations.
Papers
More filters
Proceedings ArticleDOI
Towards an emulated IoT test environment for anomaly detection using NEMU
TL;DR: A method to emulate an IoT environment using the Network Emulator for Mobile Universes (NEMU), itself built on the popular QEMU system emulator, in order to construct a testbed of inter-connected, emulated Raspberry Pi devices is proposed.
Book ChapterDOI
COCOA: A Synthetic Data Generator for Testing Anonymization Techniques
TL;DR: A framework for the generation of realistic synthetic microdata that allows to define multi-attribute relationships in order to preserve the functional dependencies of the data and proves how COCOA is useful to strengthen the testing of anonymity techniques by broadening the number and diversity of the test scenarios.
Journal ArticleDOI
TRINI: an adaptive load balancing strategy based on garbage collection for clustered Java systems
TL;DR: The results have shown that TRINI can achieve significant performance improvements, as well as a consistent behaviour, when it is applied to a set of commonly used load balancing algorithms, demonstrating its generality.
Proceedings ArticleDOI
Automated WAIT for Cloud-Based Application Testing
TL;DR: This paper presents a lightweight approach to automate the usage of expert tools in the performance testing of cloud-based applications by achieving a significant decrease in the time invested in performance analysis while introducing a low overhead in the tested system.
Proceedings ArticleDOI
Load Balancing of Java Applications by Forecasting Garbage Collections
TL;DR: The aim of this paper is to propose a new load balancing approach to improve the overall distributed system performance by avoiding potential performance impacts caused by Major Java Garbage Collection.