Jump to content

xochi

Members
  • Content Count

    845
  • Joined

  • Last visited

  • Days Won

    4

xochi last won the day on June 15 2017

xochi had the most liked content!

Community Reputation

13 Good

About xochi

  • Rank
    member

Profile Information

  • Gender
    Not Telling

FileMaker Experience

  • Skill Level
    Expert
  • FM Application
    17

Platform Environment

  • OS Platform
    X-Platform
  • OS Version
    10.13

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Did you mean to say "data writes are more expensive with Transaction Logging ON" ? If so, then I agree.
  2. 2012 Mac Mini 4/8 core i7 with 16GB RAM, internal SSD. The process showing the major slowdown is in a table where we have one field which triggers auto-enter calcs in other fields, causing many other fields to update in that table. Many of these fields pull data from related records across somewhat complex relationships that may involve 2 or more keys that are sorted. Basically, it's a combination of "read lots of data" and "write lots of data". I would presume the "write lots of data" is where the slowdown is happening, but that's just a guess.
  3. FYI, FMS 18v3 is out and fixes a subtle bug: sometimes after a reboot on macOS, the apache / httpd server fails to start up. As a result, FMPro works fine, but WebDirect will be dead, and there's no notifications. See https://community.filemaker.com/en/s/article/Software-Update-FileMaker-Server-18-0-3
  4. Update: after enabling startup restoration (transaction logging), we found that several of our long-running batch processes were about 50% to 75% slower - an operation which used to take about 100 minutes was now taking 170 minutes. We didn't notice any performance improvments, but our usage scenario doesn't typically have multiple users doing big Finds, so not clear we would have seen improvements anyway. On balance for us, this is a net loss, so we are going to turn it back off. FYI, regarding my concerns that Startup Restoration could possibly introduce new bugs, here's one examp
  5. Ok, I think we are in agreement here on the key facts. 😄 "Transaction Logging" is probably a better term to use because it conveys more information and is an established term of art: https://en.wikipedia.org/wiki/Transaction_log Although Claris does point out that their version of TL is not ACID compliant.
  6. Wim, I'm not sure we are communicating. Let me try again so that we are crystal clear: In FMS18, we have 3 "features": SR - startup restoration TL - transaction logging BPP - better parallel processing By default, SR is ON, TL is ON, and BPP is ON. The only control we users have is to enable or disable SR (we can't control TL or BPP individually). The three are linked: Disabling SR also disables TL and BPP. Claris Inc documentation notes that leaving SR on may hurt performance, and suggests turning it off - here: ht
  7. A. We guarantee better performance B. Startup Restoration may hurt performance becuase it adds extra transactional logging. C. Startup Restoration might help performance because it enables parallel processing features. A: I'm not asking for this, please don't misunderstand. B: is what Claris provides currently. C : seems to be missing from the official documentation.
  8. Definitely - which is weird that there doesn't seem to be any official statements about this - the only Claris Inc documentation I can find talks about performance problems, not benefits. Are there any official docs about this?
  9. @WimDecorte: Just to be absolutely clear - you used the term "Data Restoration" but I'm talking about "Startup Restoration" as descirbed here: https://fmhelp.filemaker.com/help/18/fms/en/index.html#page/FMS_Help/hostdb-startup-restoration.html Are you saying that if I run the command fmsadmin set serverprefs StartupRestorationEnabled=false then I may lose some benefits of parallel processing in FMS18? It's strange the Claris mentions the performance penalties, but not the possible benefits. Our UPS has 36 hou
  10. I just upgraded several servers to FMS 18, and I decided to disable this feature. My reasoning: I have not had a single one of my database servers crash in over 24 months. Startup restoration feels like a solution to a problem I'm not having. There are warnings about startup restoration causing performance hits It's a new feature, which always opens the possibility of there being some sort of subtle bugs Everyone's needs are different of course. But I would argue that if you are are having any server crashes whatsoever, you really should address
  11. How about approach it from the other direction: try using the (new in FM18) Create Data File script step followed by Write Data File, and see if the server can create a file using your file path. Maybe that will help you debug? See https://fmhelp.filemaker.com/help/18/fmp/en/index.html#page/FMP_Help%2Fcreate-data-file.html%23ww1258616 Also, I find that FMserver is sensitive to file ownership - if you right-click the file, get info in the finder, you can set the file to be owned by the 'fmserver' user. You might need to do that to the enclosing folder, too. Does that help?
  12. Some report of memory leaks in FMS 18: https://community.filemaker.com/en/s/question/0D50H0000787p8sSAA/filemaker-server-1802217-memory-leak
  13. I found this was also true with FileMaker Server 14 - you really need to run WebDirect on its own static IP address on the normal HTTPS port 443. If you don't, weird things can happen - although it may work with some clients, there may be issues for some companies that are running SSL proxy firewalls.
  14. Yes, in fact I couldn't get it working until I rebooted. I suspect that it might not survive a software update to FileMaker server, if those two files get edited during the upgrade.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.