Skip to content
This repository has been archived by the owner on Feb 11, 2021. It is now read-only.

Loading/Unloading resources from memory has a big impact on performance #334

Open
2 of 15 tasks
t3m1X opened this issue May 6, 2020 · 1 comment
Open
2 of 15 tasks
Assignees
Labels
Enhancement New feature or request

Comments

@t3m1X
Copy link
Collaborator

t3m1X commented May 6, 2020

Enhancement Description

Read title.

Type of Enhancement

Select the type of enhancement with and "x" ([x])

  • Visual
  • Physics
  • Audio
  • Particles
  • Resource Management & Save/Load
  • Materials
  • Components
  • Game Objects
  • UI/UX
  • Other

Why do you propose this enhancement?

Select why do you want to propose this enhancement with and "x" ([x])

  • Increased Performance: Optimization which would improve execution performance.
  • New Feature: It's an additional feature that fits in the product.
  • Developer Quality of Life Upgrade: It would optimize current or new implementations.
  • User Quality of Life Upgrade: It would improve the User Experience.
  • Other: Describe reason here

Implementation Instructions and Guidelines

Unloading resources could maybe be done in multithreading and avoid the hiccup.

Observations and Additional Information

Do make sure you have read the title

@t3m1X t3m1X added the Enhancement New feature or request label May 6, 2020
@t3m1X t3m1X self-assigned this May 6, 2020
@AitorSimona AitorSimona changed the title Unloading GO from memory slows down the engine Loading/Unloading resources from memory has a big impact on performance May 6, 2020
@AitorSimona
Copy link
Collaborator

:)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants