Opened 14 years ago
Closed 12 years ago
#1327 closed task (fixed)
Use DAE.Type instead of DAE.ExpType everywhere
| Reported by: | adrpo | Owned by: | adrpo |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | Backend | Version: | |
| Keywords: | Cc: | adrpo, perost |
Description
Right now we have two types: DAE.Type which we translate to DAE.ExpType.
We should *REMOVE* DAE.ExpType as the DAE.Type -> DAE.ExpType translation
consumes a lot of CPU and Memory for nothing.
Change History (3)
comment:1 Changed 14 years ago by adrpo
comment:2 Changed 14 years ago by adrpo
We decided this should not be part of White December as the type memory works rather well for now.
comment:3 Changed 12 years ago by perost
- Cc changed from adrpo, adrpo, perost to adrpo, perost
- Component set to Backend
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
The conversion DAE.Type->DAE.ExpType and storage of both these
types in env and every cref is a memory/CPU killer.
A model by Pavol Privitzer fails to flatten (as it would require 30GB of memory)
currently (trunk revision 6492), but flattens fine using ONLY 480MB if DAE.ExpType
from crefs are shared (only one unique exp type in the memory).
Conclusion: We SHOULD REALLY GET RID OF DAE.ExpType and maybe share DAE.Type.