A few people have been using the macro I wrote about in Alteryx: Wildcard Inputs, but have an issue with XLSX files. The first thing to remember is that these macros I post (on my personal blog) are examples only and are not a supported part of the product. I am happy to give people advice on how they might take what I did and extend it. However, in this case, I thought it might make a good post about Alteryx macros with optional parameters, so I went ahead and did it anyway. Continue reading
One of the really great strengths of Alteryx is that is can handle any amount of data that you throw at it. If your data is small enough, it might all be in memory, but when Alteryx gets more data than fits, it silently swaps out to disk. This way people are routinely processing data sets that are 2, 10 or even 100 times bigger than they have enough memory for!
Mostly the user never notices this aspect of the Alteryx engine and it just works. There are times though when we get feature requests that would be much easier to implement if all the data was in memory. One example of that is aggregate functions in the formula tool. Since other desktop products that are similarly easy to use, like Tableau and Excel, have simple SUM and AVG type functions in their formulas, it is assumed that Alteryx would too. Continue reading
One of the most common questions I get about Alteryx is: “How can I make my module run faster?” Although Alteryx can be very fast, since it is such a general tool, it is only as good as the module that you have authored. There is a very simple guideline that you can follow to make a module faster: do less work. The most common example of doing less work is to use the select tool as early as possible to remove fields that you are no longer using. In order to walk you through the process I use to make an Alteryx module run faster, I am going to walk through the process of optimizing my Percentile Macro to run as fast as possible.
Update – there is an updated version of this macro in the post: Alteryx: Optimizing Modules for Speed.
There was a recent question on the Alteryx forum: How to use the percentile in summarize. The question misunderstands the percentile function in the summarize and is looking for something slightly different, although with similar math. So what does the percentile in the Summarize tool do? From the help:
Percentile: Calculates the specified percentile value for the group. The percentile is calculated by sorting the data and returning the row value relative to the specified percentile and its position in the sorted array – the largest value is the 100th percentile, lowest value is the 0 percentile, median is the 50th percentile, the 25th percentile is the value in the middle of the median and minimum, etc.
The Alteryx engine is known for being fast. I would like to think that the processing engine is as fast or faster than any other data engine out there. I learned how to program on a computer with 16 KB of memory and a 2 MHz 8 bit CPU. Learning how to program in an environment like that forces you to learn how to count bits and clock cycles. Taking that mentality and applying it to a modern computer leads to very quick processing.
The difficulty though is that Alteryx is limited to the speed it can read & write data from where it is stored. Having a super fast data processing engine doesn’t help if you have to pull a terabyte of data from a data warehouse only to find a subset of it and produce a report. It doesn’t help to be fast if it is slow to get the needed data.
The Bob Cook Memorial/Mt Evans Hill Climb has long been a favorite race of mine. I am aspirationally a climber on a bike, which is to say that I am not able to compete with the people who are really good, but I love doing it anyway. I first did the race when I was 29 and did a pretty good time. When I turned 40, I decided that I would beat my time from 11 years before. It turned out that that was a slightly more difficult goal than I gave it credit for, but after 4 years of trying I finally did it and bettered that time by 2 minutes.
That was 2 years ago. This year in February I registered for the race with good intentions of getting fit and trying to do well again. Fast forward to a crazy busy summer without much time for training as well as not being very diligent in keeping the weight down and I started to think about not doing it. Instead I made the decision to go ride it just for the fun of it, and not worry about my time or anything. I am so glad I did. It is such a different experience riding that mountain without trying to go hard. My time was 36 minutes slower than last time, but at the top I felt relaxed and happy instead of ready to throw up. I had thought I might be done riding in the Mt Evans race, now I just think that I am done racing in it.
If you are a cyclist and have never ridden Mt Evans, I highly recommend it. Just don’t worry about trying to go fast, just slow down and enjoy it.