HOunza Koudelka zeigt an der FileMaker Konferenz 2016 in Salzburg wie mit FileMaker eine performante Audit Lösung gemacht werden kann.

1. Audit and
Optimization
presented by HOnza Koudelka

2. Top user complaints
about software
• It doesn’t work (it’s broken)
• It’s too complicated to use
• It’s not fast enough
Reliability
Scalability
Performance

3. Fast
/fast/
adjective
1. moving or capable of moving at high speed
“a fast and powerful car”
adverb
1. at high speed
“he was driving too fast”
2. so as to be hard to move: firmly or securely
“the ship was held fast by the anchor chain”
schnell

4. What’s schnell enough?
• Amazon discovered that for every one second
delay, conversions dropped by 7 %
• Walmart found that it gains 1 % revenue
increase for every 100 ms of improvement
• HubSpot considers the ideal page load speed
for your website's HTML to be less than 1.5
seconds
• Blink of an eye takes between 300 and 400 ms

5. Logrea Dance Academy
FileMaker Solution Optimization

6. – Dana Gioia 2007 Stanford address
“The purpose of an arts education is not to
produce more artists, though that is a
byproduct; the purpose of an arts
education is to create human beings
capable of leading successful and
productive lives in a free society.”

7. The Challenge
• FileMaker solution hosted to max 5 users by a
copy of FileMaker Pro running at front desk
• Developed and maintained by Daniel Dobkin,
Everyman Technologies, Inc.
“Champagne solutions for every budget”
• Fast enough when using locally
• Up to 40 seconds to navigate between
layouts when working over network

8. The App

9. …40 seconds later

10. Optimization Process
1. Measure
2. Find Bottleneck
3. Optimize
4. Repeat
1. Measure
2. Find Bottleneck
3. Optimize

11. What is Bottleneck?

12. What is Bottleneck?

13. What is Bottleneck?

14. Bottleneck #1

15. Navigation system…

16. Optimization #1

17. Progress

18. Bottleneck #2

19. Bottleneck #2

20. Why was it slow?

21. Why was it slow?

22. Optimization #2

23. Optimization #2

24. Final Results
Max Time Avg Time Avg Speedup
Before 2m 8s 405ms 0m 35s 360ms 723 %
After 0m 7s 18ms 0m 4s 296ms 8x faster

25. Time saved
• 5 users
• 30 seconds per layout switch
• 100 times a day
• 5 days a week
• 5 x 30 x 10 x 5 x 4 = 300 000 seconds/month
• 1000 hours a year (200 hours per user)

26. Do your own math
• Number of users: ___
• Cost per hour: ___ €
• 200 hours per user/year
• Annual savings: ______ €

27. 24U Optimization Tool
24U FM Bench lets you
• benchmark scripts & calcs
• find bottlenecks
• examine user sessions
• report results
1 611 €
+ your time

28. 24U Optimization Service
24U Software will
• examine your solution
• identify main bottleneck
• make it significantly faster
• advise how to move on
3 175 €

29. Top user complaints
about software
• It doesn’t work (it’s broken)
• It’s too complicated to use
• It’s not fast enough
Reliability
Scalability
Performance

30. Fast
/fast/
adjective
1. moving or capable of moving at high speed
“a fast and powerful car”
adverb
1. at high speed
“he was driving too fast”
2. so as to be hard to move: firmly or securely
“the ship was held fast by the anchor chain”
schnell
fest

31. Fasten your Seatbelt

33. Where’s the danger?
• Compatibility issues
• Security vulnerabilities
• Human errors
• New untrained users
• Process and rules changes
• and more…

34. Not fest enough
Audit
Update
Audit
Update
Audit
Update

35. Medeam, Air France KLM
FileMaker Solution Audit & Enhancements

36. The Challenge
• Task management & time tracking
solution designed in FM 11 in-house
by Mert Bayri, senior specialist
• Upgrade ahead
• Current version of FileMaker not yet approved
• Performance issues
• Future development & scalability concerns

37. Positive Findings
• Versioning
• Descriptive names of fields and scripts
• Low bug ratio
• Responsible approach
• Actively looking for improvements
• Thinking ahead of time

38. Outstanding benefit
Enjoyable, not boring, user interface
via seasonal decorations

39. Sample Issues
• Missing developer conventions (confirmed)
• “Spider” relationship graph
• Insufficient structure (i.e. repeating fields)
• No data change prevention/tracking
• Redundant code, no error handling
• Layout objects look and positioning
• Performance & dev effort impact of FileMaker 11

40. Before

41. After

42. Before

43. After

44. Audit Summary
• 34 pages
• 40 issues
• 40 recommendations
• guidance for months of
work

45. Outcome
• Better user experience and ease of use
• Better performance
• Better data protection
• Easier maintenance and development
• Inspiration for future improvements

46. What is it worth?
• How much do you pay to train new users?
• What’s the cost of 1-hour downtime?
• What if you can double the users efficiency?
• How much does it cost to upgrade your OS?
• How much data or time can you lose without
losing your business?

47. What is it worth?
• How much do you pay to train new users?
• What’s the cost of 1-hour downtime?
• What if you can double the users efficiency?
• How much does it cost to upgrade your OS?
• How much data or time can you lose without
losing your business?

48. Can you do it without help?
http://gtmetrix.com

50. Our Process
• Understanding the solution
• Understanding processes
• Known issues
• Environment analysis
• Code review
• Analytical tools

51. Our Focus
• Maintainability
• Scalability
• Stability & Reliability
• Security
• Usability
• Performance

52. Our Product
• Summary of issues
• Risks and liabilities
• Solution proposal
• Long-term care plan

53. Our Product
• Summary of issues
• Risks and liabilities
• Solution proposal
• Long-term care plan
3 426 €

54. 7. FileMaker Konferenz | Salzburg | 13.-15. Oktober 2016
Vortrag und Sprecher
Vielen Dank unseren Sponsoren
Danke für das Bewerten dieses Vortrages