Page Comparison

...

[ERP-MES] - Edit orders after they were created

Other improvements

[Technical] Introducing: The “meshrepair” pod. 

This is only releavant

• Reduced the time needed to process multiple 3d file at once by 50% 

Fixed Bugs

Export of all bugs that are closed, in dev, code review, testing and are assigned to 4.2: 

• Fixed a bug that caused highly detailed 3d model to time out during mesh optimization

Technical change

(This is only relevant for on premise IT-operators)

A new Pod called “meshrepair“ was introduced. It contains logic that was previously contained in the “backend“ pod. The additional pod means that the resource definition in the values.yaml file should be adjusted. Here is our minimum recommendation:

serviceConfig:    
  backend:
    resources:
      limits:
        cpu: 250m
        memory: 700Mi
      requests:
        cpu: 75m
        memory: 350Mi
    meshrepair:
      resources:
        limits:
          cpu: 4000m
          memory: 4092Mi
        requests:
          cpu: 500m
          memory: 10Mi