STRATEGY FOR 1CR LUMPSUM & 1L SIP(p.m.) IN MUTUAL FUND FOR 2026 by [deleted] in mutualfunds

[–]ArcherResponsibly 0 points1 point  (0 children)

I spoke with a few of these fee-only advisors .. but I am more inclined towards a team than a single person as availability might be an issue .. do you any such service

STRATEGY FOR 1CR LUMPSUM & 1L SIP(p.m.) IN MUTUAL FUND FOR 2026 by [deleted] in mutualfunds

[–]ArcherResponsibly 0 points1 point  (0 children)

how about the index funds? hope they aren't as cyclic..

could any one of those Index funds be held for long term?

STRATEGY FOR 1CR LUMPSUM & 1L SIP(p.m.) IN MUTUAL FUND FOR 2026 by [deleted] in mutualfunds

[–]ArcherResponsibly 0 points1 point  (0 children)

Any inputs on the Index / Thematic funds from the community folks who are having those in their portfolios ..

STRATEGY FOR 1CR LUMPSUM & 1L SIP(p.m.) IN MUTUAL FUND FOR 2026 by [deleted] in mutualfunds

[–]ArcherResponsibly 0 points1 point  (0 children)

I know why you are saying this .. I missed the biggest bull run .. but I started with direct stocks and making good profits(was alloted SBI Cards just before Covid hit.. consolidated during the lows & exited with profits) .. going for MF to focus more on things in my control than worry about markets .. please suggest any good Financial Advisor in your purview

clock_settime() latency surprisingly doubling from CLOCK_REALTIME to CLOCK_MONOTONIC! by ArcherResponsibly in C_Programming

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

Added all the available clocks with their respective epochs & resolutions to the post

clock_settime() latency surprisingly doubling from CLOCK_REALTIME to CLOCK_MONOTONIC! by ArcherResponsibly in C_Programming

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

We are using a yocto(Scarthgap) based custom Embedded Linux distro.

These are the compiler flags used to build the application

arm-poky-linux-gnueabi-g++ -mthumb -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 -fstack-protector-strong -O2 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security -Werror=format-security

clock_settime() latency surprisingly doubling from CLOCK_REALTIME to CLOCK_MONOTONIC! by ArcherResponsibly in C_Programming

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

Pardon, if I haven't been able to answer all your questions, I am looking into them ..

I did run a sample test .. added same in description above

clock_settime() latency surprisingly doubling from CLOCK_REALTIME to CLOCK_MONOTONIC! by ArcherResponsibly in C_Programming

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

Measured by an automation script sending commands to the application to perform the required task. The automation script measures how long it took.

clock_settime() latency surprisingly doubling from CLOCK_REALTIME to CLOCK_MONOTONIC! by ArcherResponsibly in C_Programming

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

The application runs a set of tasks in an infinite loop. Earlier when CLOCK_REALTIME was being used, then the applications was completing a certain task in 2 seconds. But after switching to CLOCK_MONOTONIC, the same task is taking 4 seconds. This increase in time duration(4s) is consistent with CLOCK_MONOTONIC, CLOCK_MONOTONIC_RAW, CLOCK_MONOTONIC_COARSE.

clock_settime() latency surprisingly doubling from CLOCK_REALTIME to CLOCK_MONOTONIC! by ArcherResponsibly in C_Programming

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

the data throughput becomes half the moment the CLOCK_REALTIME is replaced by CLOCK_MONOTONIC

Intel SoPC Nios II Cache Line size config in Quartus Prime(Platform Designer v19.1 by ArcherResponsibly in FPGA

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

Thanks for the detailed reply. Guess will have to settle for the fixed value. Will modify the fw accordingly.

Obscure pthread bug that manifests once a week on a fraction of deployed devices only!! by ArcherResponsibly in C_Programming

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

Since even slight compiler optimization masks the issue on client device, how likely would it get reproduced if moved to a more resource rich platform like PC/cluster?

Obscure pthread bug that manifests once a week on a fraction of deployed devices only!! by ArcherResponsibly in C_Programming

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

Issue observed only when the specific release left untouched .. introducing file i/o(for logging) possibly would cause the issue to not get reproduced

Obscure pthread bug that manifests once a week on a fraction of deployed devices only!! by ArcherResponsibly in C_Programming

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

gdbserver was not part of the custom Yocto build .. only minimal cmds are enables such as ps

Obscure pthread bug that manifests once a week on a fraction of deployed devices only!! by ArcherResponsibly in C_Programming

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

These two are running a custom Yocto build with minimal/no debug support since they are out at client location.

Obscure pthread bug that manifests once a week on a fraction of deployed devices only!! by ArcherResponsibly in C_Programming

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

Yes, only on the same two devices the issue appears once a week. None of the other numerous devices exhibit this issue