Bug 7286 - Layer item and compatibility selection performance issues
Summary: Layer item and compatibility selection performance issues
Status: VERIFIED DUPLICATE of bug 7708
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.9 M1
Assignee: Michael Wood
QA Contact: Mihail Stanciu
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-02-04 16:30 UTC by Michael Wood
Modified: 2015-09-04 09:20 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Wood 2015-02-04 16:30:29 UTC
When we're displaying layers which are compatible with the current project and come from the preferred layer source we have have to do quite a lot of work for each layer.

If we could split up the dataset by layer source and then work backwards from there if needed with an abstraction so that it's done transparently in the views/templates.
Comment 1 Michael Wood 2015-04-30 13:22:34 UTC
The toaster performance is pretty important so let's try to tackle this early on.

Toaster's recipes, machines and layers tables are all affected by this, ideally we shouldn't be blocking 5 seconds or more on retrieving this data on a 4 core/8 gig ram/ssd hardware.

I propose that all the processing on layers/equivalence/compatibility should be removed in favour of the database being re-organised so that the data in the tables maps to what toaster needs to show.
Comment 2 Michael Wood 2015-05-14 17:05:40 UTC
This issue should be fixed by the refactoring being done for bug #7708

*** This bug has been marked as a duplicate of bug 7708 ***
Comment 3 Alexandru Roman 2015-09-04 09:20:07 UTC
verified