SL21W38: Difference between revisions

From ETM
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 3: Line 3:
<br />
<br />


* Fake memory sizes:
*Fake memory sizes:
** Nearly all memory usage is caused by NMS data
**Nearly all memory usage is caused by NMS data
** Our own data/metadata is <10% of all data
**Our own data/metadata is <10% of all data
** NMS has a lot of default-value garbage
**NMS has a lot of default-value garbage
*** Mobs: clearing brain, attributes
***Mobs: clearing brain, attributes


<br />
<br />


*'''Bug: ScoreBoard of Fakes is the original scoreboard of MC. DO NOT USE'''
*Bug: ScoreBoard of Fakes is the original scoreboard of MC. DO NOT USE
**Minecraft scoreboard is bugged. Will fail on ~65k entries to be sent to clients.  (io.netty.handler.codec.EncoderException unable to fit ... into 3)
**Minecraft scoreboard is bugged. Will fail on ~65k entries to be sent to clients.  (io.netty.handler.codec.EncoderException unable to fit ... into 3)
**Do we really need the scoreboard for fakemobs? If so we need a faked / possibly static one to minimize memory garbage
**Do we really need the scoreboard for fakemobs? If so we need a faked / possibly static one to minimize memory garbage
**Change reflection calls to a faster way?
**Change reflection calls to a faster way?
**Make sure the scoreboard is not polluted with entity UUIDs / clear the scoreboard on reboot as a hotfix
**Make sure the scoreboard is not polluted with entity UUIDs / clear the scoreboard on reboot as a hotfix
*'''Bug: Every plant will result in a new renderjob being executed per player. This should not happen.'''
*Bug: Every plant will result in a new renderjob being executed per player. This should not happen.
*'''Bug: GeneralizedSuffixTree is nearly unusable on datasizes > 1000'''
*Bug: GeneralizedSuffixTree is nearly unusable on datasizes > 1000
**'''If we have ~10k users the GeneralizedSuffixTree will use up most memory on the system for all the Bin/Pod systems'''
**If we have ~10k users the GeneralizedSuffixTree will use up most memory on the system for all the Bin/Pod systems
**
**


<br />
<br />


*'''We need screen commands for players - works like Stands/Players/Mobs'''
*We need screen commands for players - works like Stands/Players/Mobs
**'''list, create, delete, info, finish, move, reset, resetelement'''
**list, create, delete, info, finish, move, reset, resetelement
**'''/screen create aldi_entry [size, design, type5, __ ]'''
**/screen create aldi_entry [size, design, type5, __ ]
***'''Creates a default-screen with the help-text to manipulate the given screen'''
***Creates a default-screen with the help-text to manipulate the given screen
**'''/screen setdesign [screen] [screendesign]'''
**/screen setdesign [screen] [screendesign]
**'''/screen settext [screen] [tilename] [colorvartext...]'''
**/screen settext [screen] [tilename] [colorvartext...]
***'''/screen settext aldi_entry {title, text, button1} [colorvartext...]'''
***/screen settext aldi_entry {title, text, button1} [colorvartext...]
***'''/screen settext aldi_entry {title, subtitle, text1, text2, text3, button1, button2,button3,} [colorvartext...]'''
***/screen settext aldi_entry {title, subtitle, text1, text2, text3, button1, button2,button3,} [colorvartext...]
**'''/screen setaction xxx'''
**/screen setaction xxx
**'''/screen settextcolor xxx'''
**/screen settextcolor xxx
**'''/screen setelementdesign xxx (button styling)'''
**/screen setelementdesign xxx (button styling)
**'''/screen setimage aldi_entry { image1 } PepeLaugh_PepeHands'''
**/screen setimage aldi_entry { image1 } PepeLaugh_PepeHands
**'''/screen setbackground aldi_entry { background } PepeLaugh_PepeHands1'''
**/screen setbackground aldi_entry { background } PepeLaugh_PepeHands1
**'''/screen hide aldi_entry {title, subtitle, text1, text2, text3, button1, button2,button3} [ON/OFF]'''
**/screen hide aldi_entry {title, subtitle, text1, text2, text3, button1, button2,button3} [ON/OFF]
**
**

Latest revision as of 23:15, 3 November 2022

◄ SL21W37 | SL21W39 ►


  • Fake memory sizes:
    • Nearly all memory usage is caused by NMS data
    • Our own data/metadata is <10% of all data
    • NMS has a lot of default-value garbage
      • Mobs: clearing brain, attributes


  • Bug: ScoreBoard of Fakes is the original scoreboard of MC. DO NOT USE
    • Minecraft scoreboard is bugged. Will fail on ~65k entries to be sent to clients. (io.netty.handler.codec.EncoderException unable to fit ... into 3)
    • Do we really need the scoreboard for fakemobs? If so we need a faked / possibly static one to minimize memory garbage
    • Change reflection calls to a faster way?
    • Make sure the scoreboard is not polluted with entity UUIDs / clear the scoreboard on reboot as a hotfix
  • Bug: Every plant will result in a new renderjob being executed per player. This should not happen.
  • Bug: GeneralizedSuffixTree is nearly unusable on datasizes > 1000
    • If we have ~10k users the GeneralizedSuffixTree will use up most memory on the system for all the Bin/Pod systems


  • We need screen commands for players - works like Stands/Players/Mobs
    • list, create, delete, info, finish, move, reset, resetelement
    • /screen create aldi_entry [size, design, type5, __ ]
      • Creates a default-screen with the help-text to manipulate the given screen
    • /screen setdesign [screen] [screendesign]
    • /screen settext [screen] [tilename] [colorvartext...]
      • /screen settext aldi_entry {title, text, button1} [colorvartext...]
      • /screen settext aldi_entry {title, subtitle, text1, text2, text3, button1, button2,button3,} [colorvartext...]
    • /screen setaction xxx
    • /screen settextcolor xxx
    • /screen setelementdesign xxx (button styling)
    • /screen setimage aldi_entry { image1 } PepeLaugh_PepeHands
    • /screen setbackground aldi_entry { background } PepeLaugh_PepeHands1
    • /screen hide aldi_entry {title, subtitle, text1, text2, text3, button1, button2,button3} [ON/OFF]