Skip to content
This repository was archived by the owner on Nov 28, 2022. It is now read-only.
This repository was archived by the owner on Nov 28, 2022. It is now read-only.

[Performance] [Remote Debug]: Performance analysis needed. Step Over takes a long time #3011

@keithchong

Description

@keithchong

Codewind version: Latest
OS: Mac (Hybrid scenario)

IDE extension version: Latest
IDE version: Eclipse, any supported version
Kubernetes cluster: OpenShift 4.3.18

Description:
Using the Codewind Microprofile project template, set a breakpoint in the Example.java code at the first line in the method example() . I had already added a println and rebuilt the project like so:

    @GET
    @Produces(MediaType.TEXT_PLAIN)
    public Response example() {
        List<String> list = new ArrayList<>();
        //return a simple list of strings
        list.add("Congratulations, your application is up and running");
        System.out.println("Test");
        return Response.ok(list.toString()).build();
    }

Step Over each line until you reach the return statement.

In my testing, the times to complete each Step Over action ranged from approximately 6 seconds to 12 seconds, so some performance analysis needs to be done to see if this can be improved. Otherwise, usability will be impacted.

Also, somewhat related, when you first run to the breakpoint, the Debug process stack takes approximately 6-8 seconds to 'refresh'.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/eclipse-ideIssue associated with the Codewind Eclipse pluginarea/iterative-devRelated to building and deploying applications (AKA "Turbine")kind/bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions