Re: V17 MSC Reports Orphaned Methods...

Hi Robert, You worry too much. Orphaned methods are nothing to lose sleep over. It’s just a 4D bug in how it handles deleting methods connected to objects. It does a less than perfect job of handling this. Sometimes it does it right, sometimes it screws up. Been this way for years in untold

Re: I've updated sideORDA

Thanks a lot Kirk. Your presentation was very instructive and useful. Patrick - Patrick EMANUEL Administrator www.association-qualisoft.eu (Soft1002, Simply Asso & QS_Toolbox) -- Sent from:

Re: I've updated sideORDA

Thanks Kirk, I was one of those that was looking for that version. I was not sure that my DM via your lists_kirk email were received. Robert > On Nov 17, 2018, at 12:57 PM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > A few folks have asked me to update sideORDA >

Re: What's the thinking on setting/clearing semaphores rapidly?

Are you able to run an A/B test? Perhaps add a bit of code that the semaphore is used on “even” hours and not used on “odd” hours. From that you might be able to measure if it makes a difference or not. Dani Beaubien Open Road Development > On Nov 17, 2018, at 11:29 AM, Kirk Brooks via 4D_Tech

I've updated sideORDA

A few folks have asked me to update sideORDA to include the examples I showed in my 4D Method presentation . I've done that

Re: What's the thinking on setting/clearing semaphores rapidly?

Good questions. I'm assuming there is some reason for the tight loop until I know better. Picking it apart bit by bit and the semaphore thing is something I recall discussion about. On Sat, Nov 17, 2018 at 10:28 AM Robert ListMail via 4D_Tech < 4d_tech@lists.4d.com> wrote: > The overall

Re: What's the thinking on setting/clearing semaphores rapidly?

The overall performance of the server is sluggish or the log writing routine? Why does the loop have to be so tight? How about writing the log every minute or every 5 minutes I suppose that’s not an option for some reason. Robert Broussard Sent from my iPhone > On Nov 17, 2018, at 10:38

Re: What's the thinking on setting/clearing semaphores rapidly?

Robert, In the absence of anything to do the process is running 4 times a second. Like I said I seem to recall discussion about setting and clearing semaphores this frequently. The overall performance is pretty sluggish and I'm looking at things that may contribute to that. On Sat, Nov 17, 2018

Re: What's the thinking on setting/clearing semaphores rapidly?

Kirk, what’s the problem with the current setup? Sent from my iPhone > On Nov 17, 2018, at 9:54 AM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > This is an obvious case for moving to a worker process once we get off v15 > but for the moment this method is causing me problems.

Re: V17 MSC Reports Orphaned Methods...

> So, any thoughts on how to get a clean bill of health from MSC…? I’ve deleted > all orphaned methods, repaired & compacted the structure. I’m running out of > things to try. Try deleting the 4D.indy then do a repair. I had a similar problem and this seemed to work for me. Neil -- Neil

What's the thinking on setting/clearing semaphores rapidly?

I'm looking at some code (v15) that writes logs on the server. It's a delay loop with a short period - 15 ticks. Within that loop a semaphore gets set, the code runs and then the semaphore gets cleared. I seem to recall hearing talk about not using semaphores in cases like this - inside really

Re: V17 MSC Reports Orphaned Methods...

Actually I was using build 229490 but now I’m using the most recent (229707) with the same behavior as previously reported. Thanks, Robert > On Nov 17, 2018, at 1:10 AM, Robert ListMail via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > While using v17R3 (Build 17.228509)