Acknowledged

Adding Fit Contributions to an existing datafield increase the PRG build time extremly

I added 3 fit contributions to my existing datafield „Edge AllinOne1“ 
and that increased the build time for the prg file from 15 seconds to 5 minutes!

https://apps.garmin.com/en-US/apps/cd433835-4089-476b-a0cf-0c13db63a18c I then did some tests and added the fit contributions one by one -
here is the result for build time:
-no Contribute at all: build time: 15 seconds -added one Contribute: build time: 1:15 minute -added 2 Contributes: build time: 2:20 minutes -added all 3 Contributes: build time 5 minutes If you want to investigate the case further, please send me a PM or an email. I would then send you the project for further investigation. Here is the code to comment out or take in contribute by contribute:

        // CONTRIBUTION+++++++++++++++++++++++++++++++++++++++++++++++++++++
        if ( showBatteryGC == true )    {
            mybatteryField = createField("devicebattery", batteryID,  FitContributor.DATA_TYPE_UINT8, {:mesgType=>FitContributor.MESG_TYPE_RECORD, :units=>"%"} );
            if ( mybatteryField != null ) {
                mybatteryField.setData(0);
            }    
        }

        if ( showShiftGC == true and gearArt > 0 )    {
            if ( gearArt == 3 ) {       // front Gear
                myfshiftField = createField("frontShift", fshiftID,  FitContributor.DATA_TYPE_UINT8, {:mesgType=>FitContributor.MESG_TYPE_RECORD, :units=>"Idx"} );
                if ( myfshiftField != null ) {
                    myfshiftField.setData(0);
                }    
            }    
            myrshiftField = createField("rearShift", rshiftID,  FitContributor.DATA_TYPE_UINT8, {:mesgType=>FitContributor.MESG_TYPE_RECORD, :units=>"Idx"} );
            if ( myrshiftField != null ) {
                myrshiftField.setData(0);
            }    
        }
        // ENDE CONTRIBUTION+++++++++++++++++++++++++++++++++++++++++++++
     


  •  
    Thank you for testing!
    Strange - but that gives hope...

    >>>That being said, what versions of Java JDK do you have installed on your machine and what type of compiler / vscode extension settings are you using?

    1) JAVA:
    I'm using Oracle Java 1.8.0_361-b09

    But I've tried other versions for testing compiler time (to no avail):
    Eclipse JDK17.0.8_7:  5 min 30 sec    (JDK because I simply accepted the suggestion for my OS)
    Oracle Java 8_241:  4 min 35 sec
    Oracle Java 8_361: 5 min 00 sec

    3) OS - Windows:
    MS WIN10 Pro  Vers.  22H2

    3) VS Code:
    VS-Code 1.81.1
    (all settings are default - I did not change anything after installation)

    3) Monkey C Extension:
    Version 1.0.9
    OptimizationLevel: Default
    Type Check Level: Default
    (all settings are default - I did not change anything after installation)

    I just set OptimizationLevel to Fast - little difference in build time: 4:30 minutes

    4) Laptop:
    Lenovo ThinkPad T570, i5-7300U, 8 GB RAM

  • Remark to Lenovo laptop: when compiling the vent goes up and makes noise - device seems very busy…