bytedeco/javacpp

Unsafe get, put and array access

Open

#156 opened on Jan 2, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (4,279 stars) (620 forks)batch import
enhancementhelp wanted

Description

Due to unsafe methods getting intensified it is faster than native. So perhaps it might be an idea to replace where appropriate with Unsafe use.

Also using Unsafe to access Java arrays is faster since there not no bound checking, memory fence and type checking.

Some native methods may be replaceable with pure Java with Unsafe.

Contributor guide

Tech stack
javacpp
Domain
performance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Understanding of Java UnsafeKnowledge of javacpp internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Investigate which native methods in the javacpp codebase can be replaced with Java Unsafe operations for performance. Look at the existing Unsafe usage in the project and consider benchmarks. The issue mentions get, put, and array access methods. Start by identifying native methods in the JNI integration and evaluating if Unsafe provides a safer speedup.