Bug 542509 - ResourceHandlerTest slow (loading a model via EMF)
Summary: ResourceHandlerTest slow (loading a model via EMF)
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: test
Depends on:
Blocks:
 
Reported: 2018-12-07 04:37 EST by Lars Vogel CLA
Modified: 2020-11-30 06:56 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2018-12-07 04:37:18 EST
ResourceHandlerTest#testProcessedApplicationModelNotNull run very long (>20 secs on my machine).

The only thing it does it loading the EMF model via ResourceHandler. I see now reason why this should take so long. Maybe we are using EMF incorrectly?
Comment 1 Lars Vogel CLA 2018-12-07 04:37:53 EST
Ed, could you have the look? ResourceHandler is located in platform UI repo.
Comment 2 Ed Merks CLA 2018-12-07 12:34:27 EST
It takes 3.72 seconds to run just this one test case for me, and when I measure it appears most of the time is spent loading classes (which makes sense given I'm running just this one test case).
Comment 3 Lars Vogel CLA 2018-12-10 11:06:31 EST
(In reply to Ed Merks from comment #2)
> It takes 3.72 seconds to run just this one test case for me, and when I
> measure it appears most of the time is spent loading classes (which makes
> sense given I'm running just this one test case).

Which OS you are using? On Windows 10 is takes ~23 seconds to run.
Comment 4 Ed Merks CLA 2018-12-10 15:03:08 EST
Windows 7 Professional.
Comment 5 Eclipse Genie CLA 2020-11-30 06:56:44 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.