ExtremeCloud IQ vs. Perforce P4

In complex environments where redundancy is required or a high density of client devices is in use. It is helpful to small enterprises with limited IT staff, as once the auto-provisioning is set up with AP templates, it means APs can be installed by non-IT staff. Licensing can be complex due to all the models, but the ability for co-term licenses to end on the same expiry is essential.

Incentivized

For large-scale codebases with fixed and regular releases that do not follow a continuous delivery paradigm, Perforce is certainly well suited. In projects that are small and distinctly separated from other discrete (though potentially dependent) units, the benefits of the Perforce tool may not be as clear of a victor over other systems.

Incentivized

• GTAC support is excellent; they understand the issue and do not hesitate to help in detail.
• The layout is very intuitive and easy to use, especially the templating of switch port types. It makes it simple to use context-based names so the purpose of the port can be understood.
• The auto channel selection now works very well, including the SDR dual 5GHz mode.

Incentivized

• Merge algorithm is smart and utilizing the visual interface to do merges makes them easier to digest.
• Easy to set up on multiple platforms and architectures and is well supported on all of them.
• Visual interface has many tools and customization options that help to optimize and personalize workflow.

Incentivized

• Licensing as a whole is a nightmare. If you have a device RMA'd - you have to email their licensing team to have the device license transferred to your new hardware. Licensing renewals are also a pain, as oftentimes they don't have the licenses correctly tied to each device you own. Definitely the biggest issue I have with ExtremeCloud IQ Networks
• Hardware is tied to you once you purchase it, so there is no resale market/secondary market for the devices you purchase - should you try to sell them when they're end of life within your organization

Incentivized

• I was having a hard time learning it. Even if you are an experienced developer, there is some learning curve.
• Can be slow when working with large data sets at once.
• When working on multiple workspaces on the same machine, Perforce can make it difficult not to mess up the code.

We have a need to consolidate into a single package, and have such a large variety of technical proficiency among our users that Perforce seems less suitable. Many would like to remain using it, however, even those who use Perforce are the minority, and are often limited to our development teams.

Incentivized

Being a web platform, it is very easily accessible. The user interface is very simple, intuitive, and visually well-designed. The learning to use it was very quick and can be done even without specific user manuals. Access to the analytics and troubleshooting tools is also extremely intuitive and very well-crafted.

Incentivized

With Perforce Helix, you can use it via the command line, via P4V, or any of the other APIs included with the product. It is extremely easy for new users to get up and running. Users of Perforce Helix only have to pull in the files of interest to them. Also, Perforce is very easy to script and integrate into your CI/CD pipeline. Streams allows you to have pinpoint control of your workflow, and P4Search is the absolute best--I wish Perforce (the company) would talk more about this. It is absolutely fabulous!

Incentivized

In our large environment, Perforce is rarely "down". We have regular maintenance windows and from time to time Perforce can feel a little slow, but its always available. Tech support has always worked with our engineers and IT department to make sure that any real performance or stability issues are addressed quickly.

Incentivized

I had two representatives from Perforce contact me after downloading it but never responded when I had questions. I also had a difficult time finding good training material for getting started. There is a lot of available support material when running into issues, though, because of how many large companies use it.

Incentivized

This rating is related to setting up an environment from an existing Perforce repository. Initial setup of Perforce as the repository for the company was done by a separate team long prior to my inception.

Incentivized

I previously used Aruba APs in the early 2010s - but have no other experience since then

Incentivized

New users of Perforce Helix can be up and running in less than thirty minutes. It is easy to use, but also very powerful. Bitbucket is slow, prone to outages, and (for large teams) requires a team of dedicated administrators. I've had request for information from Bitbucket that requires hours to pull together that would take me less than 30 seconds in Perforce Helix. Large file storage in Bitbucket is clunky and requires you to jump through too many hoops. It's not even something you have to think about with Perforce Helix, as you are only limited by your OS. Perforce Helix is very easy to use even for non-developers. I wouldn't dare ask a non-developer to store their documentation in Bitbucket.

Incentivized

• Extreme has allowed us to significantly reduce the time required for incident resolution.
• Close to zero-touch greatly enhanced our business.

Incentivized

• Locking assets make us have no merge problems which are harder to manage on other versions control without locking
• Almost no need to give support to artists or non-tech folks because the operations are very straightforward
• There's no way to do interim checkins without going to the process of creating a stream

Incentivized