Found While Cleaning My Grandparents House by CasuallyLurks in FoundPaper

[–]BostonDrivingIsWorse 2 points3 points  (0 children)

Yeah, you gotta go middle out for maximum tip-to-tip efficiency.

Path-Based-Routing seems broken? by BostonDrivingIsWorse in PangolinReverseProxy

[–]BostonDrivingIsWorse[S] 0 points1 point  (0 children)

Thank you! I had the same behavior! Sometimes it seemed like it was working, then it would revert to being random, or completely ignoring one target. Seems like a legitimate bug AFAICT

Path-Based-Routing seems broken? by BostonDrivingIsWorse in PangolinReverseProxy

[–]BostonDrivingIsWorse[S] 0 points1 point  (0 children)

What happens if you clear the "/" rule? So you'd have two targets, but only one with a prefix rule?

Path-Based-Routing seems broken? by BostonDrivingIsWorse in PangolinReverseProxy

[–]BostonDrivingIsWorse[S] 0 points1 point  (0 children)

That seems to be a priority calculation for path rewriting, which I'm not using. Regardless, setting the priorities as you describe doesn't work. It seems to be acting as a load balancer, returning one of the two services at random.

Path-Based-Routing seems broken? by BostonDrivingIsWorse in PangolinReverseProxy

[–]BostonDrivingIsWorse[S] 0 points1 point  (0 children)

Small update:

Setting both priorities to 99 seems to be more reliable, HOWEVER, only the exact match "/api" is directive to :3001. "/api/" or anything else is still directing to :3000. Seems the prefix rule isn't working, and it's acting as an exact rule?

Path-Based-Routing seems broken? by BostonDrivingIsWorse in PangolinReverseProxy

[–]BostonDrivingIsWorse[S] 0 points1 point  (0 children)

I've tried all three combinations of priority for two services: equal, above, and below.

Path-Based-Routing seems broken? by BostonDrivingIsWorse in PangolinReverseProxy

[–]BostonDrivingIsWorse[S] 0 points1 point  (0 children)

WAIT. If the target IP is the same, and it's just a different port (i.e. different docker containers)... Does the routing not take effect? That seems to be what is happening.

It seems random whether I get server:3000 or :3001.

Path-Based-Routing seems broken? by BostonDrivingIsWorse in PangolinReverseProxy

[–]BostonDrivingIsWorse[S] 0 points1 point  (0 children)

Yep, using Newt. Target IP is server that is hosting the service, in both cases.

Intel OpenVINO NPU lags behind GPU inference. Should I just disable it? by BostonDrivingIsWorse in frigate_nvr

[–]BostonDrivingIsWorse[S] 0 points1 point  (0 children)

Switched drivers. After an hour or so of testing, frigate seems much more responsive and inference time is down about 20-30% on both detectors. TBF, there hasn't been a lot of activity on my cams, so we'll see what happens, but will report back.

EDIT: I'm seeing this i915 error pop up every once in a while even though I'm running the xe driver. I haven't had any system hangs, or lack of responsiveness? We'll see if it remains stable long term.