跳至主要内容

Learn Profiling 2 -- Java

Learn Profiling 2 -- Java

Origin

This time we profiling a java program.
When I implement a problem to solve the longest-palindromic-substring problem which described in leetcode. I thought the running time should be O(n^2) and should pass the test. But result is time limit exceed. So I decide to profile my program to find out the problem.

Tool

We use a tool called JProfiler(which is very powerful but need to pay for it).

Source

Full source is at gist.

Part of code about code tuning is following(before tuning):

int len = string.length();
final LinkedList<PalindromicCenter> centers = new LinkedList<>(len * 2 - 1);
final char[] toCharArray = string.toCharArray();
{
    int j = 0;
    for (int in = 0; in < toCharArray.length - 1; in++) {
        centers.add(
        new PalindromicCenter(1, j++));
        centers.add(
        new PalindromicCenter(0, j++));
    }
    centers.add(new PalindromicCenter(1, j));
}

int maxCenterI = 0;
int max = 0;
boolean canExtend;
do {
    canExtend = false;
    for (int i = 0; i < centers.size(); i++) {
        final PalindromicCenter center = 
        centers.get(i);
        if (center.canExtend 
    && extendCenter(center, i, toCharArray, len)) {
            canExtend = true;
            if (center.maxLen > max) {
                max = center.maxLen;
                maxCenterI = i;
            }
        } else {
            center.canExtend = false;
        }
    }
} while (canExtend);

Process:

First test – LinkedList#get()

The time get cost
When we see the result, it suddenly dawn on us that our wrong selection of LinkedList cause the original time from n^2 to n^3.
So replace it with ArrayList with size will solve it.

Second test – ArrayList#size()

The time size cost
This time, we find size() also cost many time and is useless because the size will never change. So we replace the invocation with a constant variable making a step forward.

Written with StackEdit.

评论

发表评论

此博客中的热门博文

Spring Boot: Customize Environment

Spring Boot: Customize Environment Environment variable is a very commonly used feature in daily programming: used in init script used in startup configuration used by logging etc In Spring Boot, all environment variables are a part of properties in Spring context and managed by Environment abstraction. Because Spring Boot can handle the parse of configuration files, when we want to implement a project which uses yml file as a separate config file, we choose the Spring Boot. The following is the problems we met when we implementing the parse of yml file and it is recorded for future reader. Bind to Class Property values can be injected directly into your beans using the @Value annotation, accessed via Spring’s Environment abstraction or bound to structured objects via @ConfigurationProperties. As the document says, there exists three ways to access properties in *.properties or *.yml : @Value : access single value Environment : can access multi...
5 条评论
阅读全文

LevelDB Source Reading (4): Concurrent Access

In this thread, we come to the issue of concurrent access of LevelDB. As a database, it can be concurrently accessed by users. But, it wouldn’t be easy to provide high throughput under product load. What effort does LevelDB make to achieve this goal both in design and implementation? Goal of Design From this github issue , we can see LevelDB is designed for not allowing multi-process access. this (supporting multiple processes) doesn’t seem like a good feature for LevelDB to implement. They believe let multiple process running would be impossible to share memory/buffer/cache, which may affect the performance of LevelDB. In the case of multiple read-only readers without altering the code base, you could simply copy the file for each reader. Yes, it will be inefficient (though not on file systems that dedupe data), but then again, so would having multiple leveldb processes running as they wouldn’t be able to share their memory/buffer/etc. They achieve it by adding a l...
发表评论
阅读全文

LevelDB Source Reading (3): Compaction

LevelDB Source Reading (3): Compaction In the last blog that analyzes read/write process of Leveldb, we can see writing only happens to log file and memory table, then it relies on the compaction process to move the new updates into persistent sorted table for future use. So the compaction is a crucial part for the design, and we will dive into it in this blog. Compaction LevelDB compacts its underlying storage data in the background to improve read performance. The upper sentence is cited from the document of Leveldb , and we will see how it is implemented via code review. Background compaction // db_impl.cc void DBImpl :: MaybeScheduleCompaction ( ) { // use background thread to run compaction env_ - > Schedule ( & DBImpl :: BGWork , this ) ; } Two main aspects // arrange background compaction when Get, Open, Write void DBImpl :: BackgroundCompaction ( ) { // compact memtable CompactMemTable ( ) ; // compact ...
发表评论
阅读全文